pingoru pingoru Topsort had 23 outages in the last 2 years totaling 65h 40m of downtime, averaging 0.9 incidents per month.
There were 23 Topsort outages since October 22, 2024 totaling 65h 40m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident was resolved. We will keep active monitoring for a while.
Users experienced intermittent slow response times in the Oregon region, affecting about 14% of main system units in short bursts between 18:30 and 20:00 UTC. Overall availability stayed high, but some operations were briefly impacted during those periods. The engineer identified the root cause and implemented a targeted fix, restoring full performance with no further issues.
Between 2:07 AM and 2:15 AM UTC (11:07 PM – 11:15 PM CLST), our Auction Manager web application experienced intermittent availability for some users. The issue has been mitigated, and the service is now operating normally. Our engineering team is monitoring the platform closely and conducting a post-incident review to prevent recurrence. No further impact is expected at this time.
A brief service degradation occurred earlier today (18:07 - 18:13 UTC), resulting in elevated error rates on API calls for approximately 5 minutes. Engineering teams swiftly identified and resolved the issue during a routine infrastructure maintenance procedure. Services now operate at normal levels with no residual impact. Active monitoring confirms stability across all components.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Corrective action has been implemented. We are monitoring the services.
We are continuing to monitor for any further issues.
This incident has been resolved.
Our service provider for hosting our website is currently experiencing issues. We are investigating the impact.
We are continuing to investigate this issue.
The service provider has recovered and things are back to normal
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The authentication provider is having an issue. They are working on the fix.
The provider resolves the problem. We will keep monitoring.
This incident has been resolved.
Some of our services are disrupted by an upstream network and services provider (Cloudflare). They have identified a fix and we are currently monitoring for updates.
We are continuing to monitor for any further issues.
We are not receiving any more errors from our upstream network provider and things are coming back to normal. We wil keep monitoring carefully.
This incident has been resolved.
Yesterday, between 16:50 and 17:10 UTC, the Auctions and Events API experienced intermittent disruptions that affected customers using or routed through the São Paulo region.
Our Auction API service suffered issues resulting in temporary intermittences and reduced performance for some users in the Ohio region. Our team investigated and resolved the root cause. The service was returned to normal operation (20:49 UTC), and we have implemented measures to prevent similar incidents in the future.
The Auctions API service is experiencing intermittent issues. Our engineering team has identified the cause and is actively working on a solution. • Some users may notice temporary interruptions or degraded performance in auction activities. • All other platform services remain fully operational.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
The intermittent connectivity issues with the auction-engine service have been resolved. - The service is now stable and fully operational. - We are continuing to monitor the system to ensure no further disruptions occur.
We are currently investigating this issue.
The recent service disruption impacting system availability has been resolved, and all affected functionalities have been fully restored. The root cause was identified. We continue to monitor the system closely to ensure stability and performance. We appreciate the patience and understanding of all impacted users during this event.
We have identified an incident affecting connectivity related to one of our providers. ClickHouse is currently experiencing connectivity problems, and their support team is working to resolve the issue as swiftly as possible. We will continue to provide timely updates as new information becomes available and once the service is fully restored. We apologize for any inconvenience this may cause and appreciate your patience during this time.
The connectivity issue with our ClickHouse service provider has been resolved. We are currently monitoring system performance to ensure stability and smooth operation. Thank you for your patience and understanding during this incident. We will provide further updates if any additional information is necessary.
The issue has been resolved by Clickhouse, and system performance continues to be monitored to ensure stability. Please let us know if any further concerns arise.
We saw an increase in errors in the ts-ohio (us-east-2) region affecting the `/v2/auctions` and `/v2/events` endpoints which was identified at September 17th, 07:00 UTC. A fix was deployed just before 08:00 UTC. After the deployment, things came back to normal.
At September 15th 2025 – approximately between 15:30 and 16:00 UTC – certain events sent to Topsort would get a non-2xx response, pointing at an incorrect RabID. This was due to a temporary issue in the RabID verification process which was rolled back. Updates on reconciliation will follow.
We have identified minor discrepancies in the reporting api responses. We are investigating.
A fix is in place and we are updating reporting tables that might have been affected
The backfills have been done, we are reviewing the data.
We've verified that the discrepancies have been corrected.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are experiencing some issues on our reporting systems.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
An auction engine pod was failing in us-east-2 Ohio region from 8:42PM and produced some timeouts affecting customers. The issue was resolved at 9:30PM UTC-3.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to monitor for any further issues.
This incident has been resolved.