aurologic GmbH Status
Real-time updates of aurologic GmbH issues and outages
aurologic GmbH status is Operational
Core Network
FFM1 - Langen, Germany
You're checking on aurologic GmbH - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
We have identified a route leak originating from a third-party AS announcing 45.11.18.0/24, which caused an outage on certain routes affecting customer services within this prefix.
Several upstream networks failed to correctly filter the invalid announcement and subsequently propagated it, despite valid RPKI ROAs and RIR routing objects being in place for the covering prefix 45.11.16.0/22, authorizing announcements exclusively from AS30823.
The relevant transit networks have been contacted and requested to correct their filtering and routing policies, or to implement appropriate filtering where such controls are currently absent. Proper route filtering is a fundamental operational requirement for any transit network.
Please note that the underlying issue originated outside the aurologic network and was not caused by aurologic infrastructure.
We're monitoring a partial power outage in cabinet RR.A.R04.C04 due to a tripped fuse on the ATS distribution of the said cabinet, affecting about 20 dedicated servers. Our technicans looking into the issue. We have already re-enabled power and checking for the faulty server.
aurologic GmbH Outage Survival Guide
aurologic GmbH Components
aurologic GmbH Datacenter Infrastructure
AMS1 - Nikhef Housing
Cloud Storage Network
FRA1 - Tornado Datacenter FRA1
FRA2 - Interwerk Datacenter
FRA3 - Digitalrealty Frankfurt FRA16
FRA5 - Equinix Frankfurt FR7
HEL1 - Hetzner Helsinki
HEL2 - Digita Helsinki Pasila Broadcasting Tower
aurologic GmbH Network Infrastructure
Upstream Carrier
DDoS-Protection
Core Network
We have identified a route leak originating from a third-party AS announcing 45.11.18.0/24, which caused an outage on certain routes affecting customer services within this prefix.
Several upstream networks failed to correctly filter the invalid announcement and subsequently propagated it, despite valid RPKI ROAs and RIR routing objects being in place for the covering prefix 45.11.16.0/22, authorizing announcements exclusively from AS30823.
The relevant transit networks have been contacted and requested to correct their filtering and routing policies, or to implement appropriate filtering where such controls are currently absent. Proper route filtering is a fundamental operational requirement for any transit network.
Please note that the underlying issue originated outside the aurologic network and was not caused by aurologic infrastructure.
Interconnection
aurologic GmbH Public REST API
Request Handler
Scheduling Services
aurologic GmbH Cloud Infrastructure
aurologic GmbH Public Services
FFM1 - Langen, Germany
Nameservers
DNS Caches
Corporate Websites
FFM2 - Frankfurt, Germany
FFM3 - Frankfurt, Germany
my.aurologic.com
mirror.aurologic.com
EGH1 - Eygelshoven, Netherlands
aurologic GmbH Dedicated Servers
FFM1 - Langen, Germany
We're monitoring a partial power outage in cabinet RR.A.R04.C04 due to a tripped fuse on the ATS distribution of the said cabinet, affecting about 20 dedicated servers. Our technicans looking into the issue. We have already re-enabled power and checking for the faulty server.