All Systems Operational
Communications Automation Platform (CAP)
Operational
Smartflows Automation
Operational
Insights Analytics
Operational
Engage Campaigns
Operational
IntelePeer Portal
Operational
Intelepeer Portal API
Operational
List Management
Operational
AI Hub
Operational
Intelepeer LLM
Operational
Open AI
Operational
Azure Service
Operational
Smart Messaging Platform
Operational
SMS
Operational
MMS
Operational
10DLC
Operational
SMS API
Operational
Telecom Watchlist
Operational
Verizon Networks
Operational
AT&T
Operational
T-Mobile
Operational
Neustar
Operational
Lumen Toll Free
Operational
Cloud Watchlist
Operational
Deepgram
Operational
Google Services
Operational
Amazon
Operational
IBM WATSON
Operational
test deepgram
Operational
Voice Services
Operational
Chicago Switch
Operational
Dallas Switch
Operational
Denver Switch
Operational
Voice Services Portal
Operational
Switch Number Translations
Operational
Call Authentication API
Operational
CNAM Services
Operational
International Dialing
Operational
Phone Calling (PSTN)
Operational
IntelePeer.com
Operational
MS Teams
Operational
Smart Communicator
Operational
DNS Servers
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
SMS Router, Hermes, Vertical DSO, SmartFlows, List Management, DN Servers and Mixins Dec 11, 2025 20:00 - Dec 12, 2025 04:00 EST
Upcoming scheduled maintenance notice
Release includes the following:
• SMS Router - This update improves reliability and message accuracy across several areas. It includes connectivity updates to ensure continued support for partner routing, corrections to message logging for clearer reporting, proper handling of unsupported MMS numbers. Additionally, outdated MMS cache files are now automatically removed to keep the system running smoothly.
• Hermes - This release improves text-to-speech performance with new caching that speeds up repeat messages and reduces processing load. Additional enhancements provide smoother tool-based interactions, smarter handling of date prompts, and optional integration with captioning features for an improved user experience.
• Vertical DSO - This update improves appointment workflows, strengthens patient handling, and enhances overall usability. It adds simplified connection points for patient lookup and appointment management, fully integrates key DSO agent features like KPI tracking, insurance intake, provider preference handling, and Spanish language support, and includes multiple quality-of-life improvements. Additionally, creating new locations in Solutions Hub is now more reliable with better validation, consistent naming, and safeguards for unsaved changes.
• SmartFlows - This update focuses on improving clarity, flexibility, and user experience. It adds new SmartFlows variables to give builders more control, updates action labels to make flows easier to understand, and enhances the interface to better support voice options. It also includes behind-the-scenes compliance updates to strengthen system security and future-proof SmartFlows.
• List Management - Updates include backend improvements to support upcoming database upgrades, enhanced validation to prevent issues caused by special characters, and compatibility updates for the new Portal UI to ensure smooth editing and navigation within the updated interface.
• DNS Servers - Maintenance updates DNS routing and adds public resolvers to improve reliability and resolution performance. This work will be performed with full redundancy in place to minimize any service disruption.
• Mixins - Updated to improve performance, consistency, and maintainability. Enhancements include connecting to an upgraded data store, adding support for asynchronous API variable handling, simplifying service API URL structures, and standardizing log date formats for clearer traceability.
All releases and upgrades will be performed gradually across redundant segregated environments, nodes, and locations per our standard Change Management procedures. We have built in redundancy to ensure uninterrupted service—there will be active nodes, environments, and locations active at all times while the targeted nodes are upgraded. IntelePeer will always have a roll-back procedure as a standard requirement and will deploy that if there are any issues in our in-process, and post release testing.
SMS Router, Hermes,Vertical DSO, Smartflows, List Management, DN Servers and Mixins
https://docs.IntelePeer.com/atmosphere/Content/Home.htm
Posted on Dec 04, 2025 - 18:18 EST
Release includes the following:
• SMS Router - This update improves reliability and message accuracy across several areas. It includes connectivity updates to ensure continued support for partner routing, corrections to message logging for clearer reporting, proper handling of unsupported MMS numbers. Additionally, outdated MMS cache files are now automatically removed to keep the system running smoothly.
• Hermes - This release improves text-to-speech performance with new caching that speeds up repeat messages and reduces processing load. Additional enhancements provide smoother tool-based interactions, smarter handling of date prompts, and optional integration with captioning features for an improved user experience.
• Vertical DSO - This update improves appointment workflows, strengthens patient handling, and enhances overall usability. It adds simplified connection points for patient lookup and appointment management, fully integrates key DSO agent features like KPI tracking, insurance intake, provider preference handling, and Spanish language support, and includes multiple quality-of-life improvements. Additionally, creating new locations in Solutions Hub is now more reliable with better validation, consistent naming, and safeguards for unsaved changes.
• SmartFlows - This update focuses on improving clarity, flexibility, and user experience. It adds new SmartFlows variables to give builders more control, updates action labels to make flows easier to understand, and enhances the interface to better support voice options. It also includes behind-the-scenes compliance updates to strengthen system security and future-proof SmartFlows.
• List Management - Updates include backend improvements to support upcoming database upgrades, enhanced validation to prevent issues caused by special characters, and compatibility updates for the new Portal UI to ensure smooth editing and navigation within the updated interface.
• DNS Servers - Maintenance updates DNS routing and adds public resolvers to improve reliability and resolution performance. This work will be performed with full redundancy in place to minimize any service disruption.
• Mixins - Updated to improve performance, consistency, and maintainability. Enhancements include connecting to an upgraded data store, adding support for asynchronous API variable handling, simplifying service API URL structures, and standardizing log date formats for clearer traceability.
All releases and upgrades will be performed gradually across redundant segregated environments, nodes, and locations per our standard Change Management procedures. We have built in redundancy to ensure uninterrupted service—there will be active nodes, environments, and locations active at all times while the targeted nodes are upgraded. IntelePeer will always have a roll-back procedure as a standard requirement and will deploy that if there are any issues in our in-process, and post release testing.
SMS Router, Hermes,Vertical DSO, Smartflows, List Management, DN Servers and Mixins
https://docs.IntelePeer.com/atmosphere/Content/Home.htm
Posted on Dec 04, 2025 - 18:18 EST
Routing Engine Dec 11, 2025 23:00 - Dec 12, 2025 01:00 EST
Upcoming scheduled maintenance notice
Release includes the following:
• Routing Engine - Adds Do Not Originate (DNO) call screening to block calls from numbers on the industry DNO list or from invalid/fictitious area codes. Calls that are blocked will return a SIP 603 release code, ensuring compliance with FCC regulations.
All releases and upgrades will be performed gradually across redundant segregated environments, nodes, and locations per our standard Change Management procedures. We have built in redundancy to ensure uninterrupted service—there will be active nodes, environments, and locations active at all times while the targeted nodes are upgraded. IntelePeer will always have a roll-back procedure as a standard requirement and will deploy that if there are any issues in our in-process, and post release testing.
https://docs.intelepeer.com/atmosphere/Content/Home.htm
Posted on Nov 25, 2025 - 14:28 EST
Release includes the following:
• Routing Engine - Adds Do Not Originate (DNO) call screening to block calls from numbers on the industry DNO list or from invalid/fictitious area codes. Calls that are blocked will return a SIP 603 release code, ensuring compliance with FCC regulations.
All releases and upgrades will be performed gradually across redundant segregated environments, nodes, and locations per our standard Change Management procedures. We have built in redundancy to ensure uninterrupted service—there will be active nodes, environments, and locations active at all times while the targeted nodes are upgraded. IntelePeer will always have a roll-back procedure as a standard requirement and will deploy that if there are any issues in our in-process, and post release testing.
https://docs.intelepeer.com/atmosphere/Content/Home.htm
Posted on Nov 25, 2025 - 14:28 EST
External Vulnerability Scans Dec 13, 2025 10:00-18:00 EST
Upcoming scheduled maintenance notice
IntelePeer's Infosec team will be conducting routine external vulnerability scans.
All releases and upgrades will be performed gradually across redundant segregated environments, nodes, and locations per our standard Change Management procedures. We have built in redundancy to ensure uninterrupted service—there will be active nodes, environments, and locations active at all times while the targeted nodes are upgraded. IntelePeer will always have a roll-back procedure as a standard requirement and will deploy that if there are any issues in our in-process, and post release testing.
IntelePeer.com
Posted on Dec 04, 2025 - 18:21 EST
IntelePeer's Infosec team will be conducting routine external vulnerability scans.
All releases and upgrades will be performed gradually across redundant segregated environments, nodes, and locations per our standard Change Management procedures. We have built in redundancy to ensure uninterrupted service—there will be active nodes, environments, and locations active at all times while the targeted nodes are upgraded. IntelePeer will always have a roll-back procedure as a standard requirement and will deploy that if there are any issues in our in-process, and post release testing.
IntelePeer.com
Posted on Dec 04, 2025 - 18:21 EST
FCC Do Not Originate (DNO) Call Blocking Rules Dec 15, 2025 08:00-09:00 EST
IMPORTANT NOTICE: FCC Do Not Originate (DNO) Call Blocking Rules
Dear Valued Business Customer,
We are writing to inform you of an important regulatory change from the FCC that will enhance the integrity of the voice telecommunications network.
What's Changing
Effective December 15, 2025, the Federal Communications Commission (FCC) requires all voice service providers to implement Do Not Originate (DNO) blocking. This means IntelePeer and other carriers must block call attempts when the calling number is an invalid telephone number that no legitimate caller should be using.
The FCC’s summary announcement is at https://www.fcc.gov/document/fcc-announces-effective-date-providers-block-dno-list. The detailed FCC order can be reviewed at https://docs.fcc.gov/public/attachments/FCC-25-15A1.pdf
Why This Change Is Happening
This new policy is designed to combat illegal robocalling and caller ID spoofing by scammers and fraudsters. Bad actors frequently disguise their identity by spoofing phone numbers--sometimes selecting numbers randomly, which can result in the use of invalid or unassigned numbers. While it remains challenging to stop calls that spoof legitimate phone numbers, blocking calls from demonstrably invalid numbers is straightforward, as there is no legitimate reason for any caller to use such numbers.
What Constitutes an Invalid Calling Number
A phone number is considered invalid and will be blocked if the number populated in the SIP Invite’s From header matches either of the following conditions:
1. Do Not Originate Designation: The number's owner has designated it for inbound calls only, indicating that all outbound calls from that number are, by definition, unauthorized and spam.
2. Unassigned or Undefined Numbers: The number is undefined or otherwise unassigned according to the North American Numbering Plan (NANP). For example, phone numbers are invalid if they have an area code (NPA) or exchange (NPA-NXX) that does not exist in the NANP.
You are not required to use calling numbers assigned in your IntelePeer inventory. If you place calls through IntelePeer using calling numbers you procured through another number provider, that is a legitimate and valid use case. Your use of non-inventory numbers will affect whether your calls receive STIR/SHAKEN A attestation versus B attestation, but using numbers outside your IntelePeer inventory does not make them invalid, and you do not need to provide evidence to IntelePeer that you are authorized to use those numbers.
What About Private Numbering Plans
If your organization uses private numbers for internal communications (such as between company locations or applications), these numbers may appear to the network as invalid or malformed NANP numbers and will be subject to DNO blocking unless specifically addressed.
If you currently send traffic to IntelePeer using private numbering plans or custom calling number formats for internal applications, please contact IntelePeer as soon as possible to discuss accommodation options for your specific requirements.
What This Means for You
We anticipate this policy will not impact your normal business operations if your equipment is properly configured. However, if your calling equipment is transmitting invalid calling numbers due to misconfiguration, those calls will be blocked by IntelePeer or other carriers in the call path.
When Will This Change Happen
Timeline: The FCC requires all carriers to implement DNO blocking by December 15, 2025. IntelePeer will begin deploying this capability during November 2025, and some other carriers have already implemented their DNO blocking solutions.
Important: DNO blocking may already affect your calls today. Each network in the call path independently applies DNO screening, meaning a call will be blocked if any transit carrier in the route detects an invalid calling number—regardless of whether IntelePeer has completed its DNO deployment. Your outbound calls may traverse networks which already activated DNO blocking.
Action Required
We recommend that you:
• Review your voice equipment configuration to ensure all outbound calls use valid calling numbers.
• Contact your equipment vendor if you need assistance verifying your configuration
Questions or Concerns?
If you have questions about this change or experience any issues with your outbound calling service, please contact Support immediately, using one of these methods:
IntelePeer NOC Team via Email Trouble Ticketing System – support@intelepeer.com
IntelePeer NOC Team via phone – (866) 780-8639 or (720) 889-9599
Posted on Nov 18, 2025 - 14:53 EST
Dear Valued Business Customer,
We are writing to inform you of an important regulatory change from the FCC that will enhance the integrity of the voice telecommunications network.
What's Changing
Effective December 15, 2025, the Federal Communications Commission (FCC) requires all voice service providers to implement Do Not Originate (DNO) blocking. This means IntelePeer and other carriers must block call attempts when the calling number is an invalid telephone number that no legitimate caller should be using.
The FCC’s summary announcement is at https://www.fcc.gov/document/fcc-announces-effective-date-providers-block-dno-list. The detailed FCC order can be reviewed at https://docs.fcc.gov/public/attachments/FCC-25-15A1.pdf
Why This Change Is Happening
This new policy is designed to combat illegal robocalling and caller ID spoofing by scammers and fraudsters. Bad actors frequently disguise their identity by spoofing phone numbers--sometimes selecting numbers randomly, which can result in the use of invalid or unassigned numbers. While it remains challenging to stop calls that spoof legitimate phone numbers, blocking calls from demonstrably invalid numbers is straightforward, as there is no legitimate reason for any caller to use such numbers.
What Constitutes an Invalid Calling Number
A phone number is considered invalid and will be blocked if the number populated in the SIP Invite’s From header matches either of the following conditions:
1. Do Not Originate Designation: The number's owner has designated it for inbound calls only, indicating that all outbound calls from that number are, by definition, unauthorized and spam.
2. Unassigned or Undefined Numbers: The number is undefined or otherwise unassigned according to the North American Numbering Plan (NANP). For example, phone numbers are invalid if they have an area code (NPA) or exchange (NPA-NXX) that does not exist in the NANP.
You are not required to use calling numbers assigned in your IntelePeer inventory. If you place calls through IntelePeer using calling numbers you procured through another number provider, that is a legitimate and valid use case. Your use of non-inventory numbers will affect whether your calls receive STIR/SHAKEN A attestation versus B attestation, but using numbers outside your IntelePeer inventory does not make them invalid, and you do not need to provide evidence to IntelePeer that you are authorized to use those numbers.
What About Private Numbering Plans
If your organization uses private numbers for internal communications (such as between company locations or applications), these numbers may appear to the network as invalid or malformed NANP numbers and will be subject to DNO blocking unless specifically addressed.
If you currently send traffic to IntelePeer using private numbering plans or custom calling number formats for internal applications, please contact IntelePeer as soon as possible to discuss accommodation options for your specific requirements.
What This Means for You
We anticipate this policy will not impact your normal business operations if your equipment is properly configured. However, if your calling equipment is transmitting invalid calling numbers due to misconfiguration, those calls will be blocked by IntelePeer or other carriers in the call path.
When Will This Change Happen
Timeline: The FCC requires all carriers to implement DNO blocking by December 15, 2025. IntelePeer will begin deploying this capability during November 2025, and some other carriers have already implemented their DNO blocking solutions.
Important: DNO blocking may already affect your calls today. Each network in the call path independently applies DNO screening, meaning a call will be blocked if any transit carrier in the route detects an invalid calling number—regardless of whether IntelePeer has completed its DNO deployment. Your outbound calls may traverse networks which already activated DNO blocking.
Action Required
We recommend that you:
• Review your voice equipment configuration to ensure all outbound calls use valid calling numbers.
• Contact your equipment vendor if you need assistance verifying your configuration
Questions or Concerns?
If you have questions about this change or experience any issues with your outbound calling service, please contact Support immediately, using one of these methods:
IntelePeer NOC Team via Email Trouble Ticketing System – support@intelepeer.com
IntelePeer NOC Team via phone – (866) 780-8639 or (720) 889-9599
Posted on Nov 18, 2025 - 14:53 EST
DNS Servers Dec 16, 2025 00:00-04:00 EST
Upcoming scheduled maintenance notice
Release includes the following:
• DNS Servers - Maintenance updates DNS routing and adds public resolvers to improve reliability and resolution performance. This work will be performed with full redundancy in place to minimize any service disruption.
All releases and upgrades will be performed gradually across redundant segregated environments, nodes, and locations per our standard Change Management procedures. We have built in redundancy to ensure uninterrupted service—there will be active nodes, environments, and locations active at all times while the targeted nodes are upgraded. IntelePeer will always have a roll-back procedure as a standard requirement and will deploy that if there are any issues in our in-process, and post release testing.
DNS Servers
https://docs.IntelePeer.com/atmosphere/Content/Home.htm
Posted on Dec 04, 2025 - 18:24 EST
Release includes the following:
• DNS Servers - Maintenance updates DNS routing and adds public resolvers to improve reliability and resolution performance. This work will be performed with full redundancy in place to minimize any service disruption.
All releases and upgrades will be performed gradually across redundant segregated environments, nodes, and locations per our standard Change Management procedures. We have built in redundancy to ensure uninterrupted service—there will be active nodes, environments, and locations active at all times while the targeted nodes are upgraded. IntelePeer will always have a roll-back procedure as a standard requirement and will deploy that if there are any issues in our in-process, and post release testing.
DNS Servers
https://docs.IntelePeer.com/atmosphere/Content/Home.htm
Posted on Dec 04, 2025 - 18:24 EST