ARIN had 8 outages in the last 2 years totaling 131h 13m of downtime — averaging 0.3 incidents per month.
There were 8 ARIN outages since July 31, 2025 totaling 131h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating an issue preventing certain users with security keys from logging into ARIN Online.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating an issue affecting new account 2FA enablement via SMS. As a precautionary measure, new account 2FA enrollment using SMS has been temporarily disabled. New account 2FA enrollment via TOTP and hardware token is not affected. Similarly, existing SMS-based 2FA configurations remain fully operational and are not affected by this issue.
This incident has been resolved.
We are currently investigating an issue with the RPKI repositories.
This incident has been resolved.
We are unable to receive phone calls at this time. We are investigating this issue.
This has been resolved.
We had a customer report an issue that affected ARIN’s RPKI hosted system, specifically dealing with the recently released ROA Support for Transfers feature. We immediately stopped all transfers in process, confirmed only this customer was affected, and are preparing to deploy the fix.
We continue testing and have scheduled deployment of the bug fix for Monday, October 27. No RPKI customers are currently affected by this issue and measures are in place to isolate the bug until the deployment is complete.
The fix has been deployed and we are currently monitoring the RPKI Hosted system.
This incident has been resolved.
We are currently investigating degraded performance with the RPKI RRDP repository.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The chat service ARIN uses for customer support is unavailable. Please visit https://arin.net/contact for alternative options while we investigate the issue.
We have identified the issue and are implementing the fix.
This incident has been resolved.