502 errors when looking up Ukrainian IPs
- identified
We have received reports of API errors encountered when looking up Ukrainian IP addresses. We've identified the issue and are testing a fix.
- resolved
This incident has been resolved.
Loading
Applying language and content...
Loading status page
Checking service and reports...
5 Ipdata incidents · Du 2020 — official updates, affected components, duration and resolution details.
We have received reports of API errors encountered when looking up Ukrainian IP addresses. We've identified the issue and are testing a fix.
This incident has been resolved.
AWS is reporting elevated API Gateway errors in us-west-2. We have failover in place. However users may experience intermittent errors as the region comes up, and has requests routed to it, and goes down again, with in-flight requests failing before failover kicks in.
This incident has been resolved.
API requests with an empty UserAgent are returning errors. We've identified the issue and are implementing a fix.
This incident has been resolved.
Amazon's us-east-1 region had elevated errors and significantly high latency between 8.10 PM December 7th and 3.45 AM December 8th. Our systems marked the region as unhealthy and automatically re-routed traffic to other regions. You may have seen elevated errors for a short period before fail-over kicked in. Feel free to reach out to support@ipdata.co if you have any questions.
When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
As you continue to work through the incident, update your customers frequently.
Let your users know once a fix is in place, and keep communication clear and precise.
Empathize with those affected and let them know everything is operating as normal.