List Upload Degredation
This incident has been resolved.
Home
/
Status
/
Service
Email address verification service for fast, reliable, and accurate results.
Source
auto
Category
Communication
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 1h ago
6
Components
0
Active incidents
0
Maintenance
100%
90d uptime
List Upload Degredation
Jan 19, 3:17 PM
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
Showing 1 to 6 of 6 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Verification API | Operational | Component | Not recorded |
List Verification | Operational | Component | Not recorded |
Management Interface | Operational | Component | Not recorded |
ESP Integrations | Operational | Component | Not recorded |
Website | Operational | Component | Not recorded |
Documentation | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Related status pages based on category, adapter type, and operational history.
Kickbox is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
Normalized official status-page data for incidents, maintenance, components, and history.
100%
Known uptime
1 known history days
6
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
14
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Documentation
Operational
ESP Integrations
Operational
List Verification
Operational
Management Interface
Operational
Verification API
Operational
1
operational days
0
degraded days
0
outage days
0
maintenance days
89
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
This incident has been resolved.
Incident resolved. Monitoring will take place for a time to ensure functionality.
This incident has been resolved.
This incident has been resolved.
Incident resolved.
This incident has been resolved.
This incident has been resolved.
# August 21, 2024 Service Degradation Investigation **Date**: 08/21/2024 **Status**: Mitigated ### Summary A service degradation was detected by our monitoring services between 12:34 PST and 12:48 PST. We removed the impacted servers from rotation restoring full-service. We investigated and solved the issue before bringing the impacted servers back into production rotation. ### Impact API service degradation in 45-second bursts for a 12 minute period, beginning at 12:34 PST causing some requests to respond with a 502 ‘Bad Gateway’. The issue was limited to a small subset of our production servers, so fewer than 3% of global API requests during this time were affected. ### Root Cause\(s\) During a routine canary upstream service update, a small number of canary servers became unable to connect to an upstream internal service. Due to this problem, a fraction of requests to these servers caused a connection timeout, resulting in 502 Bad Gateway errors from our proxies.This problem was sporadic, so the proxies did not automatically remove these servers from rotation. ### Resolution Our internal monitoring systems detected this degradation and we worked to manually remove these servers from production rotation. This restored the API to full health. After our investigation, we resolved the communication issues with a full code re-deploy and service restart. We then ran a full suite of API health checks, confirmed the problem was resolved, and re-added the servers into production. ### Action Items We will perform a review of our internal monitoring systems to decrease the time to alert, and review our proxy health-check endpoints to see if they can be improved for partial service degradation. ## Timeline
This incident has been resolved.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Maintenance window finished. All systems operational.
Uptimus tracks the official Kickbox status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
http://status.kickbox.io
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks