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
Routing Engine Dec 2, 2025 23:00 - Dec 3, 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.
Routing Engine
https://docs.intelepeer.com/atmosphere/Content/Home.htm
Posted on Nov 21, 2025 - 17:17 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.
Routing Engine
https://docs.intelepeer.com/atmosphere/Content/Home.htm
Posted on Nov 21, 2025 - 17:17 EST
Voice Service Portal, CPaaS, DN Servers and Engage Dec 3, 2025 20:00 - Dec 4, 2025 04:00 EST
Upcoming scheduled maintenance notice
Release includes the following:
• Voice Services Portal - Users can now choose their preferred landing page—such as AI Hub, Solutions Hub, Insights, or SmartFlows—giving them quicker access to the tools they use most. This enhancement streamlines the login experience and supports a more personalized and efficient Portal workflow.
• CPaaS - This update improves reliability, observability, and overall flow stability across the platform. It introduces enhancements like new SmartFlow variables, better plugin-level traceability, and deeper operational insights through improved context tracking. Additionally, it includes a wide range of system refinements—such as security upgrades, cleaner logging, stability fixes, and codebase cleanup—to deliver a smoother and more resilient SmartFlows experience.
• 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.
• Engage - This update includes improvements across telemetry, data handling, and campaign management to strengthen overall platform reliability. Enhancements to provide clearer visibility into system behavior, while UI refinements deliver a smoother and more intuitive agent and admin experience. The release also includes targeted campaign-related bug fixes to ensure more consistent and dependable operation.
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.
Voice Service Portal,CPaaS, DN Servers and Engage
https://docs.intelepeer.com/atmosphere/Content/Home.htm
Posted on Nov 21, 2025 - 17:42 EST
Release includes the following:
• Voice Services Portal - Users can now choose their preferred landing page—such as AI Hub, Solutions Hub, Insights, or SmartFlows—giving them quicker access to the tools they use most. This enhancement streamlines the login experience and supports a more personalized and efficient Portal workflow.
• CPaaS - This update improves reliability, observability, and overall flow stability across the platform. It introduces enhancements like new SmartFlow variables, better plugin-level traceability, and deeper operational insights through improved context tracking. Additionally, it includes a wide range of system refinements—such as security upgrades, cleaner logging, stability fixes, and codebase cleanup—to deliver a smoother and more resilient SmartFlows experience.
• 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.
• Engage - This update includes improvements across telemetry, data handling, and campaign management to strengthen overall platform reliability. Enhancements to provide clearer visibility into system behavior, while UI refinements deliver a smoother and more intuitive agent and admin experience. The release also includes targeted campaign-related bug fixes to ensure more consistent and dependable operation.
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.
Voice Service Portal,CPaaS, DN Servers and Engage
https://docs.intelepeer.com/atmosphere/Content/Home.htm
Posted on Nov 21, 2025 - 17:42 EST
Routing Engine Dec 4, 2025 23:00 - Dec 5, 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.
Routing Engine
https://docs.intelepeer.com/atmosphere/Content/Home.htm
Posted on Nov 21, 2025 - 17:44 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.
Routing Engine
https://docs.intelepeer.com/atmosphere/Content/Home.htm
Posted on Nov 21, 2025 - 17:44 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