Monitoring - We are monitoring the situation further.
We have seen impact since 2026-02-25 21:00:35 (UTC+00:00).
It seems to have recovered since 2026-02-25 21:12:00 (UTC+00:00).
We have seen network-wide issues with Hetzner, which is where we host the primary backend infrastructure of our API.
This seems to have caused the mentioned impact.
Feb 25, 2026 - 21:15 UTC
We have seen impact since 2026-02-25 21:00:35 (UTC+00:00).
It seems to have recovered since 2026-02-25 21:12:00 (UTC+00:00).
We have seen network-wide issues with Hetzner, which is where we host the primary backend infrastructure of our API.
This seems to have caused the mentioned impact.
Feb 25, 2026 - 21:15 UTC
Investigating - We are currently investigating this issue.
Feb 25, 2026 - 21:09 UTC
Feb 25, 2026 - 21:09 UTC
Update - The NeoProtect team has executed parts of a multi-stage plan involving multiple options to achieve proper resilience against such incidents.
Part of this are infrastructure changes that involve egress IP changes. We advise to UPDATE YOUR IP WHITELIST as per our Docs, if you aren't using automatic updates.
Incident rates have decreased since this incident was declared, we are further monitoring the situation at all times.
There will be two further major improvements to OVH-based infrastructure, and we are also in close contact with our secondary infrastructure provider with which we are also working on reaching a, to such incidents viable, state of protection.
Both improvements should yield resilience in a redundant matter for by-default way of routing. The ETA for this is not public at this time.
In addition to that, we are consulting additional third party providers with global capacity to trial and potentially integrate globally backed solutions.
Thank you for your understanding and patience.
Feb 21, 2026 - 23:26 UTC
Part of this are infrastructure changes that involve egress IP changes. We advise to UPDATE YOUR IP WHITELIST as per our Docs, if you aren't using automatic updates.
Incident rates have decreased since this incident was declared, we are further monitoring the situation at all times.
There will be two further major improvements to OVH-based infrastructure, and we are also in close contact with our secondary infrastructure provider with which we are also working on reaching a, to such incidents viable, state of protection.
Both improvements should yield resilience in a redundant matter for by-default way of routing. The ETA for this is not public at this time.
In addition to that, we are consulting additional third party providers with global capacity to trial and potentially integrate globally backed solutions.
Thank you for your understanding and patience.
Feb 21, 2026 - 23:26 UTC
Investigating - The NeoProtect Engineering and Customer Care team is investigating these issues since first noticed on the 17th February.
We currently see momentary disconnects happening frequently within a short period of time.
While early ways to recover have not yielded proper outcomes for all single incidents, we are looking into other options to guarantee long-term stability.
This is not caused by software instability or similar, but solely due to third party infrastructure hosting our very software failing to cope with incoming attack sizes to the extent needed for us to take care of the remaining.
We have increased budget by a large amount to see to upgrade infrastructure and enact change towards its structure.
Ensure that we are working on multiple possible ways to go so that we are able to take care of such issues going forward with certainty.
We will publish further updates on the progress of the incident here.
Thank you for your understanding.
Feb 20, 2026 - 11:56 UTC
We currently see momentary disconnects happening frequently within a short period of time.
While early ways to recover have not yielded proper outcomes for all single incidents, we are looking into other options to guarantee long-term stability.
This is not caused by software instability or similar, but solely due to third party infrastructure hosting our very software failing to cope with incoming attack sizes to the extent needed for us to take care of the remaining.
We have increased budget by a large amount to see to upgrade infrastructure and enact change towards its structure.
Ensure that we are working on multiple possible ways to go so that we are able to take care of such issues going forward with certainty.
We will publish further updates on the progress of the incident here.
Thank you for your understanding.
Feb 20, 2026 - 11:56 UTC
About This Site
Welcome to NeoProtect's status page. Here NeoProtect posts about maintenances, incidents and keeps you up-to-date.
API (api.neoprotect.net)
Operational
Client Panel (panel.neoprotect.net)
Operational
Services / Products
Degraded Performance
Game Shield Service
Degraded Performance
Network Edge Locations
Operational
FRA - Frankfurt Edge Network
Operational
ASH - Ashburn Edge Network
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.