Minor · about 19 hours ago · lasted about 7 hours
Bandwidth teams are investigating an intermittent incident with Inbound Identity Headers as it relates to STIR/SHAKEN. All teams are actively working to restore expected calling behavior.
Major · 3 days ago · lasted about 2 hours
We're currently investigating an issue with the legacy WebRTC platform. Relevant teams are engaged.
Major · 3 days ago · lasted about 3 hours
Bandwidth teams have identified an incident impacting newly created Voice URI’s to be not be properly provisioned, This is resulting in inbound calls not completing as expected. Teams are actively working to restore expected behavior.
Minor · 7 days ago · lasted about 4 hours
Bandwidth teams have identified an incident impacting Advance Call Routing feature edits and/or creation. Existing voice traffic is not impacted by this incident. All teams are actively working to restore feature usability.
Major · 10 days ago · lasted about 17 hours
We are investigating a network impairment in Brazil (in the area of Manaus) with our carrier affecting voice traffic. We are currently working with our carrier for resolution.
Minor · 14 days ago · lasted about 5 hours
Bandwidth teams have identified an incident impacting voice calls transversing our ATL and JFK data centers where they may not complete as expected. All teams are actively working to normalize network behavior.
Get notified only when an outage impacts a certain component.
SaaS rules the world, and all teams depend on them to do their most productive work. IsDown helps you monitor all your cloud services, so you can focus on what matters.
Try it out! How much time you'll save your team, by having the outages information close to them?