Instabug announced $46 million in Series B funding led by global software investor Insight Partners with participation from existing investor Accel, as well as new investors Forgepoint Capital and Endeavor.
Instabug’s widely adopted bug, crash reporting, and performance monitoring solutions are essential for mobile developers and organizations which place a high value on understanding the performance of their mobile apps and the user experiences they deliver. With the new funding, Instabug will continue to aggressively execute on its mission of serving engineering teams with performance metrics and issue visibility, and product teams with customer insights and direct user feedback. By adding to its existing proactive issue detection, advanced debugging and alert management capabilities, Instabug is building the first mobile observability and performance monitoring platform.
“Mobile applications and our interactions with them have been evolving for almost 15 years, but only in the past few have these interactions become the primary way we interface with brands and services all around us,” said Omar Gabr, CEO and Co-founder of Instabug. “Leaders in industries spanning banking, transportation, retail, and education have realized mobile applications are the primary way customers will experience their brands and products. This new capital will help us develop more strategic partnerships with these enterprises as they increase investment in a mobile-first approach to customer engagement.”
“Today’s digital brands and services are increasingly demanding purpose-built mobile solutions that improve their products and experiences,” said Ganesh Bell, Managing Director at Insight Partners. “Instabug is strongly positioned to lead the nascent mobile app observability and monitoring space because the company has treated mobile as a first-class citizen since day one, and its leadership has a deep understanding of the needs faced by mobile-focused/mobile-first organizations and developers.”
“We are now at the point where mobile developers and teams can’t rely on server-side performance monitoring alone to understand and improve their app experience,” said Moataz Soliman, CTO and Co-founder of Instabug. “Mobile developers have not had access to the level of observability, performance or user-level insights that web developers have historically had when developing and improving web-based applications. We strive to give mobile teams the visibility they have been missing and are furthering our efforts to become the standard for client-side performance monitoring and management, relied on by developers and leading digital enterprises alike.”
The Latest
Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...
Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...
Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...
While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...
For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...
As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...
The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...
The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...
Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...
Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...