Developer tools
66 providers, each with the state its own status page reports.
Providers
0 with open incidents
- Apollo GraphOSOperational
- BitbucketOperational
- BitriseOperational
- BrowserbaseOperational
- BrowserStackOperational
- BuildkiteOperational
- ChromaticOperational
- CircleCIOperational
- CloudsmithOperational
- CodecovOperational
- CodemagicOperational
- CodeSandboxOperational
- ConfigCatOperational
- CoverallsOperational
- crates.ioOperational
- CrowdinOperational
- Cypress CloudOperational
- Docker HubOperational
- DopplerOperational
- env0Operational
- Expo Application ServicesOperational
- FlagsmithOperational
- GitHubOperational
- GitHub ActionsOperational
- GitLabOperational
- GitpodOperational
- Google Play ConsoleOperational
- GrowthBookOperational
- HarnessOperational
- Hex.pmOperational
- HookdeckOperational
- InfisicalOperational
- InngestOperational
- CloudBeesOperational
- JFrogMaintenance
- LambdaTestOperational
- LaunchDarklyOperational
- LinearOperational
- LokaliseOperational
- Maven Central (Sonatype)Operational
- ngrokOperational
- npmOperational
- Octopus DeployOperational
- OptimizelyOperational
- PercyOperational
- PhraseOperational
- PipedreamOperational
- PostmanOperational
- Pulumi CloudOperational
- PyPIOperational
- Red Hat Quay.ioOperational
- RubyGems.orgMaintenance
- Sauce LabsOperational
- SnykOperational
- SocketOperational
- SonarCloudOperational
- SourcegraphOperational
- SourceHutOperational
- SpaceliftOperational
- Split (Harness FME)Operational
- StatsigOperational
- SvixOperational
- Temporal CloudOperational
- HCP TerraformOperational
- Travis CIOperational
- Trigger.devOperational
Recent incidents
Last 14 days, newest first, open ones on top.
- Elevated errors on the Socket API.
Socket says it saw a period of elevated errors on its API. The provider says the issue was remedied immediately and no further impact is expected; the incident is in monitoring.
- New namespace creation restricted across few GCP regions. Impacted regions are us-central1 and europe-west3
Temporal Cloud says new namespace creation is temporarily restricted in GCP regions us-central1 and europe-west3 due to compute capacity constraints, while existing namespaces operate normally. The incident is in monitoring.
- SocketOperationalElevated errors on the Socket API.
- GitHubMajor outageIncident with Git Operations and Pull Requests
- GitHubPartial outageDegraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot
GitHub says Copilot availability was degraded for GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces due to an issue with an upstream model provider. GitHub says the issue has been mitigated and it is monitoring to ensure stability.
- OptimizelyDegradedOptimizely Graph in EMEA - Intermittent performance issues
Optimizely says Optimizely Graph in the EMEA region had intermittent performance issues on 2026-11-09, including a brief recovery followed by a return to degradation. As of 23:36 UTC, the provider says service is restored and it is monitoring for stability.
- InngestDegradedInvestigating Degraded Performance
- GitHubMajor outageIncident with Actions and Checks API
- CloudsmithDegradedIncrease in 503 errors for NPM requests
- OptimizelyDegradedOptimizely Graph in EMEA - Intermittent performance issues
- LaunchDarklyDegradedEmail notifications are not being delivered
- GitHubPartial outageIncident with Webhooks and Actions
- OptimizelyDegradedB2B Environment down, not accessible - Multiple environments affected
- GitHubDegradedIncreased timeouts due to surge in anonymous users
GitHub says it is investigating reports of impacted performance for some of its services, with the incident titled "Increased timeouts due to surge in anonymous users." The current status is investigating.
- InngestOperationalInvestigating System Degradation
Inngest says it investigated a service degradation reported at 11:19 UTC on 2026-11-08. The incident is now resolved, with no further details given in the updates.
- GitHubDegradedIncrease in timeouts for some unauthenticated users
GitHub says an increase in timeouts affected some unauthenticated users, with degraded performance of API Requests and some GitHub services. It identified a problematic component and redeployed it, and the incident is now resolved. A root cause analysis will be shared later.
- BitrisePartial outageBuilds failing while downloading tools from GitHub
Bitrise says builds failed while downloading tools from GitHub because of an ongoing GitHub incident. GitHub has mitigated it, failure rates are back to normal, and the incident is resolved. Builds that failed can be restarted.
- npmDegradedMinor issues impacting package publish
The provider says it had minor issues impacting package publish on npm. It investigated, implemented a fix and monitored the results, and the incident is now resolved as of 2026-11-07 15:05 UTC.
- ChromaticDegradedUpstream provider causing performance degradation
Chromatic says performance degradation was caused by an upstream provider, with the incident now resolved. The provider says performance has returned to normal and it is working through the backlog of builds caused by the upstream incident.
- PhraseDegradedSecurity Incident Affecting Phrase User Accounts
- BitriseDegradedInterrupted builds and longer queue times
- Temporal CloudDegradedSome customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures
Temporal Cloud says some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures. The provider identified the issue and applied a mitigation, and it is now monitoring the results.
- HarnessOperationalapidocs.harness.io not responding to HTTPS requests
Harness says apidocs.harness.io was not responding to HTTPS requests, starting around 00:59 UTC on 2026-11-06. The provider identified the issue and implemented a fix, and it reports the incident resolved at 07:13 UTC the same day.
- SourceHutDegradedgit.sr.ht under high load
SourceHut says git.sr.ht is under very high load, causing intermittent service disruptions. The provider attributes this to a combination of external factors, says it is working on mitigations, and lists the incident as investigating.