Incident History
Aug 20, 2026
yesterday
Resolved · August 20, 3:36 PM GMT+2 (after 1h 12m)
Status changed: partial outage → operational
Investigating · August 20, 2:24 PM GMT+2
Status changed: operational → partial outage
Aug 18, 2026
3 days ago
Resolved · August 18, 4:27 PM GMT+2 (after 3h 1m)
Status changed: partial outage → operational
Investigating · August 18, 1:26 PM GMT+2
Status changed: operational → partial outage
Aug 15, 2026
5 days 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
18 days 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
28 days 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
1 month 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
1 month 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
1 month 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
1 month 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
1 month 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
1 month 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
1 month 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
1 month 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
1 month 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
1 month 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
1 month 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
1 month 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
1 month 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
2 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
2 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