Is Prompt.io Down Right Now? Check if there is a current outage ongoing.

Our upstream provider indicates that normal operational status has returned. We will be crediting customers with affected broadcasts. If you have an affected broadcast, please attempt to retarget the messages that failed with the 35125 error code.

There is a problem some customers are experiencing due to an issue with an upstream messaging partner. This is resulting in improper error code (35125) being returned during some broadcasts. We are working with the upstream provider to get this resolved as soon as possible. Suggest pausing large outbound broadcasts while this is being resolved.

The fix has been deployed. All previously sent smart links via broadcast now redirect correctly. Thank you for your patience while the team sorted out this important issue.

A fix has been found -- estimated time to normal operation of about 1 hour from now.

Smart links sent via broadcast text are causing errors for some customers. We have identified the issue and are actively working on a solution.

Incident Resolved by T-Mobile.

We have been informed that T-Mobile has finally resolved 10DLC delivery issues. All operations now normal.

We have reports that messages to T-Mobile are flowing again. However, we are still testing and are keeping the incident open until tomorrow morning out of an abundance of caution. We believe all messaging delivery to T-Mobile will be resolved shortly. Thank you for your patience and understanding.

We continue to see sporadic delivery issues to a subset of T-Mobile customers. This seems to affect a small number of T-Mobile subsidiaries. This has been identified as a problem at the carrier (T-Mobile) network level and is being widely reported by our upstream partners. We will keep an eye on this and update accordingly.

We are experiencing deliverability issues for SMS and MMS to some T-Mobile handsets due to upstream carrier issues. We are monitoring closely. Texts to T-Mobile handsets may return inappropriate 30003 error messages while this issue is being resolved by our upstream partners.

Carriers have informed us that MMS delivery delays have subsided and throughput is now at normal levels. Note that during the 2022 General Election through November 8, MMS delivery is expected to experience several periods with significant carrier delays or throughput limitations.

There are upstream delivery delays of up to 30 minutes at the carriers (AT&T, T-Mobile, Verizon, etc.) for MMS messages due to excessive election traffic. For more information on carrier delays, visit: https://prompt.stonly.com/kb/guide/en/understanding-message-delivery-delays-YDsM4NldNt/Steps/1984631

Upstream partners report normal delivery times for outbound messaging.

We are continuing to monitor. Outbound message delays are still occurring.

In some instances, an upstream provider is causing delays in message delivery. Some customers have reported message delays of up to 15 minutes. We are monitoring closely. Messages sent through Prompt are eventually getting delivered.

A patch for this issue has been released for all customers. Imports from CSV are now correctly importing data fields.

An issue has been identified with new CSV imports. Data fields are not being properly imported. Please avoid data imports via CSV while this issue is being investigated and fixed.

The backlog of provisioning issues are clearing. However, the carriers and upstream partners have informed us that there are several "manual" steps that are slowing down the provisioning process. We are closely monitoring the situation and working to expedite provisioning of new phone numbers where possible. It is unlikely, but possible, that new organizations provisioning for the first time may take a week or more to become fully operational on registered 10DLC.

We are seeing some phone number assignments process today, albeit slowly. Some assignments have been processing in 30 minutes. There are still latent issues with assignments that were requested several days ago still "stuck" in Pending status at the carriers. We are in constant communication with our upstream partners on this issue. Thank you for your patience.

Number provisioning is slow with our upstream providers. We continue to work with with the carriers to ensure that numbers can be provisioned in a normal time frame.

Our upstream messaging providers are experiencing delayed assignment of 10DLC numbers to messaging campaigns. The providers are working to resolve the issue. This is the same issue that was occurring last week. For existing 10DLC phone numbers, no impact is expected.

We are finally(!) seeing somewhat normal times to provision and activate new 10DLC numbers. It only took the carriers and our upstream providers 5 days to get it sorted. Thank you for your patience and understanding.

There are still some delays in new number provisioning with our upstream carrier partners. We expect this to finally get this matter resolved today. Newly provisioned numbers are being cleared from the carrier backlog regularly, but there are still some outstanding issues here that we're tracking closely.

There are still some lingering issues with new some phone number purchases for SMS getting connectivity through Campaign Registry and upstream providers. These seem to be clearing slowly. We expect full resolution soon. Existing channels are not experiencing any issues.

Delays for provisioning new numbers are clearing up, but there are still some issues when provisioning new SMS and MMS enabled 10DLC numbers in the platform due to upstream carriers. We continue to monitor.

Issues with newly provisioned 10DLC SMS channels are still occurring with our upstream providers. There are no issues sending or receiving texts from previously provisioned phone numbers prior to Monday June 6. We will update when we hear progress from the carriers on this issue.

Our upstream SMS and MMS provider is experiencing issues when provisioning new text phone numbers. Newly provisioned channels in Prompt may not become usable today as they work through this issue. We are in contact with the upstream providers and are closely monitoring the situation. The upstream provider is undergoing maintenance on this issue with expected delays in provisioning continuing through Tuesday, June 7 11:45pm. We are sorry for the inconvenience. Previously provisioned channels are all working as expected. Only channels provisioned today are experiencing these issues.

The incident has been resolved. A short term hiccup with services at AWS caused a problem. Normal service should now be restored for all customers.

We are currently investigating an issue where a small number of customers are experiencing latency and/or an inability to log in.

An SSL security certificate expiration issue caused temporary issues for some customers. This was quickly resolved.

This incident has been resolved and normal operations have resumed for all customers. Thank you for your patience and understanding.

The issue has been identified and a fix is being implemented.

One of the Prompt.io servers is experiencing issues. A small subset of customers may be experiencing service unavailability. We are actively addressing the issue.

Messaging delivery speeds seems to have returned to normal with our partners downstream.

A messaging partner has informed of us delays and timeouts with increased transaction times in their messaging platform. They are working on a resolution and we will update once we receive feedback from their teams.

This incident has been resolved.

The upstream issues with delayed delivery from our messaging providers seem to have cleared. All messaging is operating normally now. Have a great weekend.

Several upstream telephony providers are reporting delays in delivery and issues. See https://www.prompt.io/status-page for status from our various telephony partners. We will update you as we learn more information. Most have identified and deployed fixes, though we are still monitoring their completeness.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

Investigating an incident affecting the ability to open all Instant Apps and Prompt Exchange. Texts that do not utilize instant apps or smart links are unaffected

AWS is experiencing a major outage that is affecting and impacting all Prompt.io customers. We are investigating and working on this to mitigate downtime.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We have restarted services. We will continue to monitor and have plans to help rectify the situation this evening.

We are continuing to investigate this issue.

We are investigating

We have brought the site back up and are operational. We will continue to monitor the situation and work to determine the root cause so we can get a fix implemented.

We are restarting our site to restore availability

We are continuing to investigate this issue.

We are experiencing some performance issues. Investigating...

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

Things are looking back to normal. We will continue to monitor

We are looking into an issue where we are seeing degraded performance with some of our services.

This incident has been resolved.

We have rectified the issue and are monitoring.

We are experiencing some intermittent issues and working to resolve the problem.

Things are still looking normal. Moving this to resolved.

We have restarted services and the system is functioning normally. We will continue to monitor.

We are continuing to investigate this issue.

Our system is currently overloaded and not responsive when reading/writing data. We are restarting some of the services to try and remedy the issue.

The font vendor SSL issues have been resolved.

Our platform relies on a third-party vendor for icons. This vendor is experiencing SSL issues which is causing our platform to load without icons being visible. We are monitoring status from the icon vendor infrastructure provider here: https://status.stackpath.com/incidents/22c999cbl1nh This does not affect API functionality for our platform.

This incident has been resolved.

The site is operational again. We are monitoring and investigating root cause.

Our service is currently experiencing problems. We are investigating and working to fix the issue.

This incident has been resolved.

We have released a fix to the bug we experienced today and will monitor. Site has been in good health for remainder of day.

Our system has been restored to working order. We have identified a bug in our software that caused the previous disruption. We are working on a fix and will deploy it shortly.

We are experiencing an issue on one of our servers that is causing some service disruptions for a portion of our customers. Working to resolve now.

This incident has been resolved.

We have restored services to working order. We are continuing to monitor the situation.

We are currently investigating an issue on production that has disrupted our service.

No further javascript snippet issues in the last 60 mins. Considering this resolved.

We have deployed a fix and are monitoring the situation.

The issue has been identified and a fix is being implemented.

We have identified an issue causing degraded performance with apps executing Javascript snippets on the Chatbox Platform. We are working to resolve it now.

We have monitored the fix and consider this issue resolved.

A fix has been deployed to address the locking scenario that caused an availability issue to some of our customers. We will continue to monitor as this use case gets reenabled during business hours.

Our services our operation again (as of 2:17pm PT). We have identified a deadlocking issue we are working to resolve. We have paused the use case that was identified as causing the deadlock. We will be re-enabling this use case once we have deployed a fix.

The issue has been identified and a fix is being implemented.

We are have identified an issue causing pages to not load or be extremely delayed to some of our customer base.

Issue confirmed. No systems were impacted and the follow-on testing came back successful

We are investigating StatusPage.io posting to the #alerts channel in Chatbox Slack