Outages · APIs: messaging, media, analytics
Operational Bandwidth outage dossier
bandwidth.com · Official status page (Statuspage-compatible JSON)
Official status now
Operational Operational
checked 0 min ago How we score status
All Systems Operational
Read just now from: Official status page (Statuspage-compatible JSON) · official page ↗
ORBIT score
Clear skies: official status: Operational
At a glance
90-day timeline (1 day tracked)
Each bar is a day. Green: our checks found no official incident. Amber/red: the provider reported one. Grey: before ORBIT started tracking this service. This is "share of our checks with no official incident", not the provider's SLA.
Official incidents per week
Impact mix, 90 d
- 19 none
- 12 minor
- 8 major
- 11 critical
Visitor reports, last 24 h
Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.
Incident history
- → resolved · lasted 7.4 hBandwidth Local Market Impairment - 922 - Cincinnati, OHnone resolved · 922 - Cincinnati, OH · official notice ↗ · replay & discuss
- → resolved · lasted 20.5 hBandwidth Local Market Impairment - 635 - Cedar Rapids, IAnone resolved · 635 - Cedar Rapids, IA · official notice ↗ · replay & discuss
- → resolved · lasted 19 minJFK Data Center Incidentminor postmortem · Inbound Calling (SIP) - United States, Outbound Calling (SIP) - United States · official notice ↗ · replay & discuss
- → resolved · lasted 2.2 hBandwidth Local Market Impairment - 122 - Manchester, NHnone resolved · 122 - Manchester, NH · official notice ↗ · replay & discuss
- → resolved · lasted 39 minInbound Calling - Caller ID Lookup (CNAM) APImajor postmortem · Inbound Calling - Caller ID Lookup (CNAM) · official notice ↗ · replay & discuss
- → resolved · lasted 18 hBandwidth Local Market Impairment - 330 Evansville, INcritical resolved · 330 - Evansville, IN · official notice ↗ · replay & discuss
- → resolved · lasted 2.2 h911 Address Provisioning & Lookup Incidentmajor postmortem · 9-1-1 Call Routing Service, 9-1-1 Provisioning Service · official notice ↗ · replay & discuss
- → resolved · lasted 2 hBandwidth Local Market Impairment - 668 - Tucson, AZnone resolved · 668 - Tucson, AZ · official notice ↗ · replay & discuss
- → resolved · lasted 31.5 hToll-Free Port Order Activation Delaysminor postmortem · Number Porting · official notice ↗ · replay & discuss
- → resolved · lasted 6.4 hBandwidth Local Market Impairment - 548 - Wichita Falls, TXnone resolved · 548 - Wichita Falls, TX · official notice ↗ · replay & discuss
- → resolved · lasted 29 minBandwidth Ticketing Supportcritical resolved · Ticketing Support, Help Center · official notice ↗ · replay & discuss
- → resolved · lasted 6.2 hBandwidth Local Market Impairment - 122 - Manchester, NHnone resolved · 122 - Manchester, NH · official notice ↗ · replay & discuss
- → resolved · lasted 28.2 hBandwidth Local Market Impairment - 538 Tulsa, OKcritical resolved · 538 - Tulsa, OK · official notice ↗ · replay & discuss
- → resolved · lasted 2.9 hBandwidth Appcritical postmortem · Bandwidth App · official notice ↗ · replay & discuss
- → resolved · lasted 0 minIntermittent Call Failuresnone postmortem · official notice ↗ · replay & discuss
- → resolved · lasted 3.4 hAT&T SMS Delaysminor postmortem · SMS Messaging (SMPP) · official notice ↗ · replay & discuss
- → resolved · lasted 2.3 hJFK Calling Incident - Inbound/Outbound Callingminor postmortem · Inbound Calling (SIP) - United States, Outbound Calling (SIP) - United States · official notice ↗ · replay & discuss
- → resolved · lasted 9 hBandwidth Local Market Impairment - 536 - Oklahoma City, OKcritical resolved · 536 - Oklahoma City, OK · official notice ↗ · replay & discuss
- → resolved · lasted 24 hToll-Free Port Activation Delaysminor postmortem · Number Porting · official notice ↗ · replay & discuss
- → resolved · lasted 2.8 hBandwidth Local Market Impairment - 532 - Wichita, KSnone resolved · 532 - Wichita, KS · official notice ↗ · replay & discuss
- → resolved · lasted 4.6 hBandwidth Local Market Impairment - Grand Island, NEnone resolved · 646 - Grand Island, NE · official notice ↗ · replay & discuss
- → resolved · lasted 2.3 hBandwidth Local Market Impairment - 256 Clarksburg WVcritical resolved · 256 - Clarksburg, WV · official notice ↗ · replay & discuss
- → resolved · lasted 5.7 hBandwidth Local Market Impairment - 248 - Richmond, VAnone resolved · 248 - Richmond, VA · official notice ↗ · replay & discuss
- → resolved · lasted 5.1 hVoice Authentication Incident - Pindropmajor postmortem · Inbound Calling (SIP) - United States · official notice ↗ · replay & discuss
- → resolved · lasted 11.7 hOutbound 10DLC MMS Delivery Incident - T-Mobile, Verizon, AT&Tmajor postmortem · MMS Messaging (MM4) · official notice ↗ · replay & discuss
Related services
- Degraded / minor incidentTwilioDegraded / minor incident→
- Degraded / minor incidentSendGridDegraded / minor incident→
- OperationalMailgunOperational→
- no official feedPostmarkno official feed→
- no official feedMailchimpno official feed→
- OperationalVonage APIOperational→
- OperationalPlivoOperational→
- OperationalBird (MessageBird)Operational→
"Runs on" links are inferred from public information and may be outdated.
How we score status
- Source. Every reading comes from the provider's own public status page or status API (Statuspage, Instatus, incident.io-style JSON, or the provider's RSS/JSON). ORBIT never pings or scans the service.
- Scope. For each open incident we count the regions or components it names against the total the provider publishes, and label it global, multi-region, 1 region or n of N components.
- Age. Incidents are new (under 1 hour), active, long-running (open more than 48 hours) or stale (no provider update for 24 hours or more).
- Headline. The headline colour comes from current incidents only. A single-region or small-scope incident caps the headline at "Degraded"; a global or widespread one keeps the provider's impact. Long-running or stale issues limited to one region or a few components get a known long-running issue badge and don't set the headline colour.
- Transparency. The provider's own page-level status is always shown next to ORBIT's headline, with a link to the official page. When they differ, the provider's page is the authority on what it says.
Where this data comes from. "Official status" is read from each provider's own public status page or status API (the same JSON or RSS their status page publishes), cached for a minute or more. ORBIT never pings, scans or probes the provider's systems. "Our checks" and history are ORBIT's own record of those readings, kept in our database. Visitor reports are unverified. Headlines are matched by name and shown for context: coincidence, not causation. Cloudy_Day is independent and not an official source for any company listed.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.