Affected components
Update timeline
- investigating Apr 27, 2026, 01:05 PM UTC
Bandwidth teams are investigating an outbound messaging incident, where customers are experiencing unexpected 4452 error codes. Teams are working to restore expected messaging behavior.
- investigating Apr 27, 2026, 03:55 PM UTC
Teams continue to investigate this incident.
- investigating Apr 27, 2026, 07:04 PM UTC
Teams continue to investigate this incident.
- identified Apr 27, 2026, 07:59 PM UTC
Teams have identified the source of this incident and are working to restore expected network behavior.
- identified Apr 28, 2026, 12:27 PM UTC
Trams continue work to resolve this incident. Ongoing mitigation work is underway.
- identified Apr 28, 2026, 05:52 PM UTC
Trams continue work to resolve this incident. Ongoing mitigation work is underway.
- monitoring Apr 28, 2026, 06:56 PM UTC
Teams are observing expected messaging behaviors, and will continue to monitor for stability.
- monitoring Apr 29, 2026, 05:02 PM UTC
Teams continue to observe expected messaging behaviors, and will continue to monitor for stability.
- resolved Apr 30, 2026, 03:57 PM UTC
This incident has been resolved.
Looking to track Bandwidth downtime and outages?
Pingoru polls Bandwidth's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Bandwidth reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Bandwidth alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required