Incident History
Aug 15, 2026
3 months ago
Resolved · August 16, 1:02 AM GMT+2 (after 1h 36m)
Status changed: partial outage → operational
Investigating · August 15, 11:25 PM GMT+2
Status changed: operational → partial outage
Aug 3, 2026
3 months ago
Resolved · August 3, 4:06 AM GMT+2 (after 9 minutes)
Status changed: major outage → operational
Investigating · August 3, 3:56 AM GMT+2
Status changed: operational → major outage
Jul 23, 2026
3 months ago
Resolved · July 24, 11:51 AM GMT+2 (after 15h 13m)
Status changed: degraded performance → operational
Investigating · July 23, 8:38 PM GMT+2
Status changed: operational → degraded performance
Jul 22, 2026
4 months ago
Resolved · July 22, 4:31 PM GMT+2 (after 56 minutes)
Status changed: degraded performance → operational
Investigating · July 22, 3:34 PM GMT+2
Status changed: operational → degraded performance
Jul 22, 2026
4 months ago
Resolved · July 22, 2:56 PM GMT+2 (after 21 minutes)
Status changed: degraded performance → operational
Investigating · July 22, 2:34 PM GMT+2
Status changed: operational → degraded performance
Jul 20, 2026
4 months ago
Resolved · July 20, 6:07 PM GMT+2 (after 3h 44m)
Status changed: major outage → operational
Investigating · July 20, 2:23 PM GMT+2
Status changed: operational → major outage
Jul 20, 2026
4 months ago
Resolved · July 20, 1:03 PM GMT+2 (after 21 minutes)
Status changed: major outage → operational
Investigating · July 20, 12:41 PM GMT+2
Status changed: operational → major outage
Jul 17, 2026
4 months ago
Resolved · July 17, 10:56 AM GMT+2 (after 8 minutes)
Status changed: major outage → operational
Investigating · July 17, 10:47 AM GMT+2
Status changed: operational → major outage
Jul 14, 2026
4 months ago
Resolved · July 14, 4:12 AM GMT+2 (after 11 minutes)
Status changed: partial outage → operational
Investigating · July 14, 4:01 AM GMT+2
Status changed: operational → partial outage
Jul 14, 2026
4 months ago
Resolved · July 14, 3:41 AM GMT+2 (after 26 minutes)
Status changed: partial outage → operational
Investigating · July 14, 3:14 AM GMT+2
Status changed: operational → partial outage
Jul 8, 2026
4 months ago
Resolved · July 8, 5:37 AM GMT+2 (after 2h 7m)
Status changed: partial outage → operational
Investigating · July 8, 3:29 AM GMT+2
Status changed: operational → partial outage
Jul 6, 2026
4 months ago
Resolved · July 6, 2:43 AM GMT+2 (after 37 minutes)
Status changed: partial outage → operational
Investigating · July 6, 2:06 AM GMT+2
Status changed: operational → partial outage
Jul 5, 2026
4 months ago
Resolved · July 5, 8:13 AM GMT+2 (after 1h 13m)
Status changed: partial outage → operational
Investigating · July 5, 6:59 AM GMT+2
Status changed: operational → partial outage
Jun 28, 2026
4 months ago
Resolved · June 28, 9:56 PM GMT+2 (after 9 minutes)
Status changed: major outage → operational
Investigating · June 28, 9:47 PM GMT+2
Status changed: operational → major outage
Jun 27, 2026
4 months ago
Resolved · June 27, 3:19 AM GMT+2 (after 40 minutes)
Status changed: major outage → operational
Investigating · June 27, 2:39 AM GMT+2
Status changed: operational → major outage
Jun 23, 2026
4 months ago
Resolved · June 23, 1:00 PM GMT+2 (after 1h 13m)
Status changed: major outage → operational
Investigating · June 23, 11:47 AM GMT+2
Status changed: operational → major outage
Jun 18, 2026
5 months ago
Resolved · June 18, 12:39 PM GMT+2 (after 50 minutes)
Status changed: partial outage → operational
Investigating · June 18, 12:12 PM GMT+2 (23 minutes earlier)
Status changed: major outage → partial outage
Investigating · June 18, 11:49 AM GMT+2
Status changed: operational → major outage
Jun 17, 2026
5 months ago
06/18/2026, 11:00 AM - 01:00 PM GMT+2
Resolved · June 18, 1:36 PM GMT+2 (after 2h 35m)
Dear Sir or Madam,
The scheduled maintenance has been successfully completed.
The relocation of our SIM hosting infrastructure to the new data center was carried out as planned and without any issues. All affected SIM cards and services are fully operational again.
No further action is required on your part. If you experience any unexpected issues, please contact our support team.
Thank you for your patience and understanding.
Kind regards,
Your seven.io Team
In Progress · June 18, 11:00 AM GMT+2
Maintenance has started.
Scheduled · June 17, 11:20 AM GMT+2
Dear Sir or Madam,
On June 18, 2026, we will be relocating our SIM hosting infrastructure to a new data center. This move will enhance service reliability and lay the foundation for the further expansion of our platform.
Maintenance Period
June 18, 2026, from 11:00 AM to 1:00 PM
Affected SIM Cards
This affects SIM cards currently operating on our existing hosting infrastructure. Not all customers or SIM cards are affected by this measure.
Impact
The affected SIM cards will be temporarily unavailable during the maintenance period. No connections can be established via the affected SIM cards during this time.
Once the migration is complete, the SIM cards will automatically be brought back online. In most cases, no action is required on your part.
Should you continue to experience service disruptions after the maintenance window has ended, please contact our support team.
Thank you for your understanding.
Kind regards,
Your seven.io Team
Jun 12, 2026
5 months ago
06/13/2026, 01:00 AM - 02:00 AM GMT+2
Resolved · June 13, 1:12 AM GMT+2 (after 11 minutes)
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.
In Progress · June 13, 1:00 AM GMT+2
Maintenance has started.
Scheduled · June 12, 4:52 PM GMT+2
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.
Jun 11, 2026
5 months ago
Scheduled server maintenance
Maintenance06/12/2026, 01:00 AM - 02:00 AM GMT+2
Resolved · June 12, 5:39 AM GMT+2 (after 4h 39m)
The maintenance appointment concludes without incident.
In Progress · June 12, 1:00 AM GMT+2
Maintenance has started.
Scheduled · June 11, 11:06 AM GMT+2
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.