Swagger Outage History

19 incidents recorded over the last 365 days, 16 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Swagger status100.00% uptime history

Every Recorded Swagger Incident

Swagger incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 14, 2026Swagger Catalog outageThis incident has been resolved.2 minResolved
Sep 26, 2026Portal and Swagger Studio Maintenance: 26th of SeptemberThe scheduled maintenance has been completed.3h 0mScheduled
Sep 19, 2026Explore and Swagger Studio Maintenance: 19th of SeptemberThe scheduled maintenance has been completed.2h 0mScheduled
Aug 24, 2026SwaggerHub API Editor — Issue InvestigatingSome users may see a blank or unresponsive page when opening the API editor on app.swaggerhub.com. Our team is actively investigating. Issue started ~10:30 UTC following a scheduled release.-121 minResolved
Aug 18, 2026Swagger Studio - Intermittent 502sWe experienced intermittent availability issues affecting our front-end services. Our team identified the issue, took corrective action, and confirmed service stability following the event.-209 minResolved
Aug 18, 2026Swagger Studio - 502sWe experienced intermittent availability issues affecting our front-end services. Our team identified the issue, took corrective action, and confirmed service stability following the event.-868 minResolved
Aug 18, 2026Investigating — Delayed webhook delivery, and verification resultsThis incident has been resolved.1h 2mResolved
Aug 18, 2026SwaggerHub — Intermittent 502 ErrorsBetween 06:18–06:35 AM CEST, some users may have experienced intermittent 502 errors on app.swaggerhub.com; the issue was caused by an unexpected traffic spike, resolved automatically, and no data loss occurred.-212 minResolved
Aug 13, 2026Partial outage: contract publishing and deployment checksWe have resolved the issues. It is our goal to provide the highest level of uptime and reliability so we can consistently serve our customers. For additional support, please reach out to Customer Care via…33 minResolved
Aug 11, 2026Swagger Studio - Web application unavailableThis incident has been resolved.1h 32mResolved
Aug 7, 2026SwaggerHub API Editor IssuesThe incident has been resolved.1h 48mResolved
Jul 25, 2026SmartBear ID MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jul 14, 2026Issues in connecting to the Pactflow UI in certain regionsThis incident has been resolved.17h 55mResolved
Jul 8, 2026Errors publishing contracts to PactFlowThis incident has been resolved.24h 8mResolved
Jun 8, 2026Intermittent 403 errors from GitHub ActionsWe worked with our providers/vendors to implement a solution and the issue has now been resolved. If you are still experiencing 403 errors, please reach out to Customer Care via https://support.smartbear.com/pactflow/.434h 20mResolved
Dec 22, 2025Swagger Studio - Web applicationThis incident has been resolved.2h 45mResolved
Nov 26, 2025Swagger Explore OutageThis incident has been resolved.38 minResolved
Nov 18, 2025Custom Domains IssueThis incident has been resolved.2h 45mResolved
Nov 13, 2025Degraded PerformanceFollowing the hotfix implementation, the issue has been resolved. Our team continues to closely monitor the environment to ensure system stability7h 42mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Swagger incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Swagger Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Swagger acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Swagger outage in this window ran 18d 2h, against a mean recovery of 1d 9h. If you depend on Swagger in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.