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
Nov 2025
No notices reported this month
Oct 2025
- ResolvedResolved
Resolved
What Occurred: At 8:30 AM ET on October 10th, 2025, our email filtering service began experiencing significant delays and delivery failures to our client-facing support mailboxes as a result of the widespread AWS US-East-1 outage that morning. This includes support@oit.co, success@oit.co, porting@oit.co, billing@oit.co, sales@oit.co, and compliance@oit.co.
Who is Affected: All partners and clients attempting to contact OIT support
When It Began: 8:30 AM ET, 10/20/2025
Current Status:
This is considered Resolved.
AWS and our email filtering service have confirmed full functionality has been restored. We've re-enabled our email filtering service and confirmed inbound emails are being received.
Next Steps:
If you submitted a support request via email between 8:30 AM ET and 12:30 PM ET and never received a case confirmation email response, please re-send your email to confirm it was received on our end.
Next Update: N/A
- IdentifiedIdentified
What Occurred: At 8:30 AM ET, our email filtering service began experiencing significant delays and delivery failures to our client-facing support mailboxes as a result of the widespread AWS US-East-1 outage this morning. This includes support@oit.co, success@oit.co, porting@oit.co, billing@oit.co, sales@oit.co, and compliance@oit.co.
Who is Affected: All partners and clients attempting to contact OIT support.
When It Began: 8:30 AM ET, 10/20/2025
Current Status: We have disabled the email filtering service and restored deliverability to the affected mailboxes as of 12:30 PM ET. We are currently working with our email filtering service's support to complete the delivery of all emails sent to the affected mailboxes during this window.
Workarounds: For urgent requests that were sent during this window that cannot wait until the emails are restored, please re-send the email or call our support at 305-967-6756.
Next Steps: Continuing to work with vendor support to ensure all emails are delivered.
Next Update: We will provide an update when all emails during the affected period are restored.
We appreciate your patience throughout this process. If you need additional support, please contact support@oit.co.
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.
![[object Object]](/_next/image?url=https%3A%2F%2Finstatus.com%2Fuser-content%2Fv1744123237%2Fq0sngloyv09z4rkjf5gg.png&w=3840&q=75)