Incident History

Maintenance has been completed successfully. All web services, including the dashboard, documentation, knowledge base, MCP server, and voice tester tool, are fully operational again. Message delivery remained unaffected throughout the entire window. Thank you for your patience.

Maintenance has started.

Following up on this week's maintenance, an additional maintenance window is required tonight between 01:00 and 02:00 CEST to complete the remaining work. Some of our web-based services may be unavailable for a few minutes during this window, specifically the dashboard (app.seven.io), the documentation and knowledge base, the MCP server, and the voice tester tool.

Message delivery itself is fully unaffected: SMS sending, voice calls, and all API endpoints (HTTP API, SMPP, inbound processing) remain operational at all times. There is nothing you need to do, and no messages will be delayed or lost.

The actual downtime will most likely be far shorter than the maintenance window itself. If anything seems off once the maintenance is complete, our support team is happy to help.

The maintenance appointment concludes without incident.

Maintenance has started.

We will be performing scheduled maintenance tonight between 01:00 and 02:00 CEST. During this window, a brief interruption of a few minutes may occur for the following services: dashboard (app.seven.io), documentation, knowledge base, MCP server, and the voice tester tool.

Core messaging operations are not affected. SMS sending and delivery, voice calls, and all API endpoints (HTTP API, SMPP, inbound processing) will continue to operate without interruption throughout the maintenance window. No action is required on your part, and no messages will be delayed or lost.

We expect the actual interruption to be significantly shorter than the announced window. Should you experience any issues after the maintenance has been completed, please don't hesitate to reach out to our support team.

What happened

A failure in one of our network switches disrupted the routing of inbound SMS traffic for a subset of numbers on our platform. As a result, some inbound messages were delayed or could not be delivered during the incident window.

Outbound SMS and all other services remained fully operational throughout the incident.

We are continuing to review the incident internally and evaluating additional safeguards to reduce the likelihood and impact of similar failures in the future.

We understand the importance and reliability requirements of inbound messaging and sincerely apologize for the disruption and inconvenience this incident may have caused.

If you have any questions or continue to experience issues, please contact our support team.

Thank you for your patience and continued trust.

After identifying the faulty network component, our engineering team restored the affected routing path and verified normal inbound SMS processing across the platform. Service has since been fully restored.

A failure in one of our network switches is disrupting the routing of inbound SMS to a subset of phone numbers. Our team is working to restore the affected component and bring inbound SMS back to full service. We will post another update as soon as the issue is resolved.

We are currently experiencing a partial outage affecting inbound SMS to a subset of phone numbers. Messages sent to the affected numbers may be delayed or fail to be delivered. Outbound SMS and all other services remain fully operational.

Our team has identified the cause and is actively working to restore full service. We will post updates as soon as more information is available.

We apologize for the inconvenience and appreciate your patience.

Status changed: partial outage → operational

Status changed: operational → partial outage

Status changed: partial outage → operational

Status changed: operational → partial outage

Status changed: partial outage → operational

Status changed: operational → partial outage

Status changed: partial outage → operational

Status changed: operational → partial outage

What happened:
Our monitoring system detected elevated error rates in voice message delivery and consequently automatically reported an outage. In reality, the voice platform remained available at all times.

Background:
The issue was triggered by an unusual delivery pattern from a single customer, whose high error rate temporarily skewed the aggregated success metrics that our monitoring system evaluates. For all other customers, the voice service was not affected at any time.

What we’re improving:
We’re looking into how we can more clearly distinguish anomalies in individual accounts from platform-wide issues in the future, so that our status reports more accurately reflect the actual service experience.

Status changed: partial outage → operational

Status changed: operational → partial outage

On February 1, 2026, between 7:58 and 14:30, there was a temporary disruption affecting SMS delivery. During this period, only a limited number of SMS messages were successfully sent. We apologize for any inconvenience caused. The service is now fully restored.

We would like to inform you about a temporary service disruption affecting our Voice Gateway. Between 12:58 CET and 13:03 CET, the gateway was unable to process calls.

The root cause of this incident was identified as a temporary overload of the memory interface, which prevented normal call execution during this period.

We sincerely apologize for any inconvenience this may have caused and want to assure you that we have taken measures to prevent similar occurrences in the future.

Thank you for your understanding.

Due to a power supply disruption, a portion of the hosted SIMs was unavailable for one hour.

An unexpected failure of network interfaces occurred on our main server, resulting in extended outages. We have now restored operations. There are still performance issues in some areas, which we are working on resolving. Such repeated outages are very stressful for us. Therefore, we are now massively expanding our infrastructure and converting it to a highly available cluster environment. We will keep you regularly updated on the progress of this upgrade so that you are always aware of the measures we are taking to prevent similar problems in the future.

We regret to announce that there were repeated disruptions to the main server between October 13th and 15th:

October 13th, 2025, 9:01 PM – Main server down, incident listed on the status page, duration: approximately 8 hours.
October 14th, 2025, 6:54 PM – Disruption of individual services, no incident update listed on the status page, duration: approximately 1 hour.
October 15th, 2025, 11:35 PM – Disruption of individual services, no incident listed on the status page, duration: approximately 15 minutes.
October 16th, 2025 - Minor performance losses, no downtime recorded.

We apologize for any inconvenience and thank you for your understanding.

Between October 13, 2025, 21:06 UTC+2 and October 14, 2025, 05:11 UTC+2, one production node became unresponsive due to an unexpected system failure.
The node was restored to normal operation, and all services have been stable since.
Further investigation is underway to identify the underlying cause.

This incident has been resolved.

This incident has been resolved, all systems are running. Thank you for your patience and understanding.

We are continuing to investigate this issue.

We are currently experiencing a major outage affecting our main gateway. Our technical teams are actively investigating the root cause and working to resolve the issue as quickly as possible.

We understand how critical our services are to your operations and sincerely apologize for the inconvenience. We are treating this with the highest priority and will provide regular updates.

You can follow live updates on status.seven.io.

Thank you for your patience and understanding.

This morning we had a disruption on the inbound servers from 9am to 9:45am. The problem has been resolved and all systems are working properly again.

Some services have been experiencing performance issues over the last hour. We have resolved the issue and apologize for any inconvenience.

This morning some customers may have expected a false response from our SMS API. The problem has been solved within two hours and everything should be back to normal. Thank you for your understanding.

On August 10, 2024, our database server had a replication error, causing a problem in the data transfer. Some of our applications query data from the replication to relieve the load on the productive main server. The server is now under extended monitoring. No further disruptions are expected in this regard.

The incident has been fixed. All systems are reachable again

There is currently a fault on one of the switches in our data center which may lead to poor accessibility of our services. Our technicians are working at full speed to analyze the cause and fix the problem. Please be patient. As soon as new information is available, we will inform you on this website. Please excuse the inconvenience. Thank you for your understanding.

The SMS delivery to the O2 network in Germany is operating in regular performance again.

Currently we experience SMS delivery delays when sending messages to O2 Network in Germany. Our engineers are working with our carrier partner to resolve the issue. We will provide another update as soon as more information becomes available.

This incident has been resolved. We do not experience any unusual traffic anymore. So far we managed to block a total of about 3.000.000 requests within a couple of minutes and blocked about 10.000 hosts. Nevertheless we continue extensive monitoring of all systems.

Unfortunately today we are experiencing several DDoS attacks on our servers. Teams are working hard to mitigate/manage. This is causing a lot of high load, or connection issues. Currently our systems are working at normal rates again. Thank you for your patience.