![[object Object]](/_next/image?url=https%3A%2F%2Finstatus.com%2Fuser-content%2Fv1744123237%2Fq0sngloyv09z4rkjf5gg.png&w=3840&q=75)
Ashburn (IAD) Voice - Operational
Ashburn (IAD) Voice
Atlanta (ATL) Voice - Operational
Atlanta (ATL) Voice
Phoenix (PHX) Voice - Operational
Phoenix (PHX) Voice
Messaging (SMS/MMS) - Operational
Messaging (SMS/MMS)
Native Fax - Operational
Native Fax
API - Operational
API
Call Recording (IAD) - Operational
Call Recording (IAD)
Call Recording (PHX) - Operational
Call Recording (PHX)
Call Recording (ATL) - Operational
Call Recording (ATL)
Device Provisioning (NDP) - Operational
Device Provisioning (NDP)
Manager Portal - Operational
Manager Portal
Manager Portal Pro - Operational
Manager Portal Pro
SNAPmobile - Operational
SNAPmobile
SNAPmobile Web - Operational
SNAPmobile Web
VoIPMonitor (QoS) - Operational
VoIPMonitor (QoS)
CloudieConnect - Operational
CloudieConnect
CloudieAI - Operational
Notice history
Sep 2025
- ResolvedResolved
What Occurred: We have identified that the upstream CNAM database provider is intermittently providing incorrect Caller ID Name information after performing a CNAM dip.
Who is Affected: All partners and clients.
When It Began: 9:30 AM ET, 9-15-25
Current Status:This is considered Resolved.
Bandwidth has informed us that after working with their upstream CNAM database provider they were able to correct the inbound CNAM discrepancies.
We have confirmed we are seeing proper inbound CNAM at this time.
Next Steps:
If you continue to experience incorrect inbound CNAM, Bandwidth has requested that any new incorrect inbound CNAM lookups be provided to them.
If you have any examples please email support@oit.co and provide the caller number, called number, date and time along with the caller ID that was displayed and what it should have been.
Next Update: N/A
- IdentifiedIdentified
What Occurred: We have identified that the upstream CNAM database provider is intermittently providing incorrect Caller ID Name information after performing a CNAM dip.
Who is Affected: All partners and clients.
When It Began: 9:30 AM ET, 9/15/2025
Current Status: Bandwidth has internally escalated this with their engineers as well as with their new upstream CNAM DB provider.
Workarounds: There are no known workarounds at this time.
Next Steps: Bandwidth has requested that any new incorrect inbound CNAM lookups be provided to them. If you have any examples, please email support@oit.co and provide the caller number, called number, date and time, along with the caller ID that was displayed and what it should have been.
Next Update: We will provide an update when new information becomes available.
We appreciate your patience throughout this process. If you need additional support, please contact support@oit.co.
- InvestigatingInvestigating
What Occurred: We have identified that the upstream CNAM database provider is intermittently providing incorrect Caller ID Name information after performing a CNAM dip.
Who is Affected: All partners and clients.
When It Began: 9:30 AM ET, 9/15/2025
Current Status: Bandwidth has confirmed that the upstream CNAM/LIDB database provider is having a broad issue, and they are investigating internally.
Workarounds: There are no known workarounds at this time.
Next Update: We will provide an update when new information becomes available.
We appreciate your patience throughout this process. If you need additional support, please contact support@oit.co.
Aug 2025
- ResolvedResolved
This incident is now considered resolved. We will continue to monitor for the next 24 hours.
We appreciate your patience throughout this process. If you need additional support, please contact support@oit.co.
- UpdateUpdate**What Occurred:** We are currently experiencing a service disruption affecting The Campaign Registry (TCR) platform. This impacts the ability to create new 10DLC campaigns, register new brands, or edit existing campaigns. **Who is Affected:** All partners and clients who need to create new TCR/10DLC campaigns, register new brands, or modify existing campaign configurations. **When It Began:** 9:31 AM ET, 8-21-25 **Current Status:** * TCR has confirmed a platform-wide issue affecting campaign management functions * OIT is actively working with TCR support to monitor the situation * No updates have been provided by TCR at this time * You can follow along for live updates from TCR at [Campaign Registry Status](https://status.campaignregistry.com/#) **Workarounds:** There are no workarounds available for campaign creation or editing at this time. Please plan accordingly for any urgent campaign needs. **Next Steps:** * We recommend postponing any planned campaign creation or modifications until service is restored * OIT will continue monitoring the situation and provide updates as information becomes available **Next Update:** 3:15 PM ET, 8-21-25
- IdentifiedIdentified
What Occurred: We are currently experiencing a service disruption affecting The Campaign Registry (TCR) platform. This impacts the ability to create new 10DLC campaigns, register new brands, or edit existing campaigns.
Who is Affected: All partners and clients who need to create new TCR/10DLC campaigns, register new brands, or modify existing campaign configurations.
When It Began: 9:31 AM ET, 8-21-25
Current Status:
TCR has confirmed a platform-wide issue affecting campaign management functions
OIT is actively working with TCR support to monitor the situation
No estimated time of resolution has been provided at this time
Workarounds: There are no workarounds available for campaign creation or editing at this time. Please plan accordingly for any urgent campaign needs.
Next Steps:
We recommend postponing any planned campaign creation or modifications until service is restored
OIT will continue monitoring the situation and provide updates as information becomes available
Next Update: We will provide an update within 1 hour or when new information becomes available
Offline Services:
TCR Campaign Creation
TCR Brand Registration
TCR Campaign Editing/Modifications
Degraded Services:
None
Operational Services:
SMS/MMS message sending and receiving (all existing campaigns continue to function normally)
All other messaging services
All voice services
All portal services
Important Note: This outage does NOT affect your ability to send or receive messages. All existing registered campaigns continue to operate normally.
We appreciate your patience throughout this process. If you need support, please contact support@oit.co. For more real-time status updates as well as discussion please join our Discord.
Jul 2025
- CompletedJuly 19, 2025 at 4:30 AMCompletedJuly 19, 2025 at 4:30 AMMaintenance has completed successfully
- In progressJuly 19, 2025 at 3:30 AMIn progressJuly 19, 2025 at 3:30 AMMaintenance is now in progress
- PlannedJuly 19, 2025 at 3:30 AMPlannedJuly 19, 2025 at 3:30 AM
On Friday, July 18, 2025, at 11:30 PM ET, we’ll be performing routine maintenance on the CloudieConnect system to help ensure continued performance and reliability.
During this time, CloudieConnect users may experience a brief service interruption (up to 5 minutes) during which login access and the ability to make or receive calls may be temporarily unavailable.
All other services will remain fully operational and unaffected.
We appreciate your patience throughout this process. If you need additional support, please contact support@oit.co.
- ResolvedResolved**What Occurred:** At 2:37 PM ET, all calls on the GRR server began to fail. **What was Affected:** * Inbound and Outbound Calls on GRR **When It Began**: 7/8/2025 2:37 PM ET **Current Status**: This incident is now Resolved. **Next Steps:** Major Incident Report will be available within 48 business hours.
- UpdateUpdateWe implemented a fix and are currently monitoring the result.
- MonitoringMonitoring**What Occurred:** At 2:37 PM ET, inbound and outbound calls to GRR began receiving a 503 error, causing them to fail. **What Is Affected:** Inbound and outbound calls to the GRR server **When It Began:** 2:37 PM ET on July 8, 2025 **Next Update:** July 9, 2025 at 4:00 PM ET **Current Status:** We have restarted the NMS service on the GRR server and are showing calls processing successfully again. **Next Steps:** * We will continue to monitor to ensure that calls continue to process successfully. We will also continue investigating the root cause of the failure. * Devices that were registered on GRR may need to be restarted after the NMS service restart took place. **Next Update:** July 9, 2025 at 4:00 PM ET