Live Developer Tools Outage Feed
Real-time intelligence on the developer infrastructure that ships your code, version control, package registries, hosting, and backend platforms.
This week's developer tools outage roundup →- Maintenance
Upgrade Shared Pooler V1 to V2 for us-east-1 region
THIS IS A SCHEDULED EVENT Jun 1, 13:00 - 15:00 UTCMay 18, 02:57 UTCScheduled - There will be scheduled maintenance on 2026-06-01 from 13:00-15:00 UTC (09:00-11:00 EDT) on the Shared Pooler(V1) for the us-east-1 region.This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime.The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected:
us-east - Maintenance
Upgrade Shared Pooler V1 to V2 for us-west-1 region
THIS IS A SCHEDULED EVENT May 28, 16:00 - 18:00 UTCMay 18, 02:55 UTCScheduled - There will be scheduled maintenance on 2026-05-28 from 16:00-18:00 UTC (09:00-11:00 PDT) on the Shared Pooler(V1) for the us-west-1 region.This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime.The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected
us-west - Maintenance
Upgrade Shared Pooler V1 to V2 for eu-west-1 region
THIS IS A SCHEDULED EVENT May 27, 13:00 - 15:00 UTCMay 18, 02:52 UTCScheduled - There will be a scheduled maintenance on 2026-05-27 from 13:00-15:00 UTC on the Shared Pooler(V1) for the eu-west-1 region.This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime.The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected:Only projects c
eu-west - Maintenance
Upgrade Shared Pooler V1 to V2 for eu-central-1 region
THIS IS A SCHEDULED EVENT May 26, 13:00 - 15:00 UTCMay 18, 02:49 UTCScheduled - There will be a scheduled maintenance on 2026-05-26 from 13:00-15:00 UTC on the Shared Pooler(V1) for the eu-central-1 region.This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime.The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected:Only project
eu-central - Info
Build Failures for Some Next.js Deployments
May 22, 17:11 UTC Resolved - Between 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up deployments should no longer encounter this error.
- Degraded
Branch creation degradation
May 21, 16:46 UTCInvestigating - We are seeing degradation in branch creation linked to database migration locks. We are investigating and will share further updates as progress is made.
- Degraded
Elevated Build Errors
May 21, 15:01 UTCIdentified - We are currently investigating elevated build failures affecting a subset of Vite projects. Affected deployments may be timing out. We’ve identified an issue and are working on the fix.
- Degraded
Elevated error ratio for web service
May 21, 2026 09:42 UTCInvestigating - We're investigating for the root cause of elevated error rates for webservice.You can follow the progress and updates here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22182
- Degraded
Login issues for SSO and Email accounts on Supabase Dashboard
May 21, 08:33 UTCUpdate - We are currently investigating an issue causing login failures for some users attempting to authenticate to the Supabase dashboard via SSO or email/password login flows.Affected users may see an error similar to:“captcha protection: request disallowed (sitekey-secret-mismatch)”Currently logged-in users are not affected, and GitHub authentication continues to operate normally.We will continue to provide updates as more information becomes available.May 21, 08:30 UTCInvestigating - Users that are already logged in are not affected.
- Degraded
Network restrictions preventing read replica communication
May 20, 21:04 UTCInvestigating - Network restrictions are preventing read replicas from communicating with their primaries for a limited number of customer projects. We are actively investigating this issue.
- Info
Missing Build CPU Minutes Usage Data
May 20, 20:07 UTCMonitoring - We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.
- Degraded
Incident with Actions
May 20, 16:58 UTCInvestigating - We are investigating reports of degraded performance for Actions
- Degraded
Paused Projects Showing Incorrect Resume Deadline
May 20, 15:40 UTCInvestigating - We are currently investigating a UI issue affecting paused projects, where an incorrect resume deadline is displayed in the dashboard.The message incorrectly states that projects can be resumed within 90 days while also displaying today’s date as the expiry date.For example:“All data, including backups and storage objects, remains safe. You can resume this project from the dashboard within 90 days (until 20 May 2026). After that, this project will not be resumable, but data will still be available for download.”Please note this is a display issue only. Projects
- Degraded
Elevated response times affecting origin services
May 19, 21:08 UTCInvestigating - We are investigating elevated latency and errors affecting origin services. This is currently impacting request performance and may result in degraded experience or failures for some users.
- Degraded
Degraded performance with Create API
May 19, 18:18 UTCInvestigating - Investigating: We’re seeing degraded performance with create.netlify.com. Some customers are seeing issues with latency or 500 errors while accessing the create.netlify.com
- Degraded
Elevated Build and Functions Deployment Errors
May 19, 17:30 UTCResolved - Between 17:38 and 17:57 UTC, we experienced elevated error rates affecting the Build Pipeline. Some customers may have encountered failed deploys or HTTP 500/503 errors during deployment processing. The systems are recovering and we're continuing to investigate the root cause
- Degraded
Degraded performance with Create API
May 19, 14:37 UTCMonitoring - A fix has been implemented and we are monitoring the results.May 19, 14:31 UTCIdentified - The issue has been identified and a fix is being implemented.May 19, 14:26 UTCInvestigating - We’re seeing degraded performance with create.netlify.com. Some customers are seeing issues with latency or 500 errors while accessing the create.netlify.com.
- Major
Log ingestion issues
May 18, 23:26 UTCInvestigating - Customers may experience delayed log ingestion or periods where logs are unavailable. We will provide updates while we work to resolve the issue.
- Degraded
React Router 7 function invocation errors
May 18, 21:53 UTCIdentified - The issue has been identified and a fix is being implemented.May 18, 21:42 UTCInvestigating - We're investigating an issue where customers are currently experiencing application failures due to function invocation errors when using React Router 7.
- Degraded
Support cases cannot be submitted
May 18, 15:17 UTCMonitoring - We have implemented a fix. New support cases can be created. We continue to monitor.May 18, 15:00 UTCInvestigating - We are investigating an issue where support cannot be submitted through the dashboard.
- Info
Jobs not being picked up/stuck pending
May 18, 2026 11:03 UTCIdentified - We've identified the root cause of some jobs not getting picked up due to runner pool exhaustion. We're working on getting more runners added to the pool.More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145
Other live feeds
Continuously updated from official provider status pages.