Real-time monitoring of all Aevum News platforms and services
🕐Last updated: Just now
📊99.97% uptime (30 days)
📅
🖥️ Component Status
Content Delivery
Main Website (aevumnews.com)
Operational
Mobile Web / Responsive
Operational
Global CDN (CloudFront)
Operational
Applications
iOS App
Operational
Android App
Operational
Push Notifications
Operational
Backend & APIs
REST API (api.aevumnews.com)
Operational
GraphQL Endpoint
Operational
Database Cluster
Operational
Core Services
Content Publishing System
Operational
Live Streaming Engine
Operational
Search & Indexing
Operational
⚡ Active Incidents
⚠ Minor
Elevated Response Times on EU Region CDN
Some users in Europe are experiencing slower page loads due to routing anomalies in our Frankfurt edge location.
CDNEU Region
🕐 2 hours ago — Monitoring
🔴 Major — Resolved
Breaking News Feed Delivery Interrupted
The real-time breaking news feed experienced intermittent failures affecting push notifications and live widgets.
Push NotificationsLive Feed
🕐 Yesterday — Resolved
ℹ Info — Resolved
Scheduled CMS Database Migration
A routine database optimization caused brief read latency in the content management system. No impact to end users.
CMS Internal
🕐 3 days ago — Resolved
🔧 Scheduled Maintenance
Jul 15, 2025 — 02:00 UTC
CDN Certificate Rotation
SSL/TLS certificates across all edge nodes will be renewed. No expected downtime.
Planned
Jul 22, 2025 — 03:00 UTC
Database Cluster Scaling
Vertical scaling of primary database nodes to support increased Q2 traffic. Expected 2-minute API latency spike.
Planned
Jul 3, 2025 — Completed
Authentication Provider Upgrade
OAuth provider updated to support SSO integrations. Completed ahead of schedule.
Completed
📈 Performance (24h)
47ms
Avg Response
99.98%
Success Rate
2.4M
Requests/Hr
14ms
P95 Latency
⚠ Minor — Monitoring
Elevated Response Times on EU Region CDN
📅 June 30, 2025 at 14:23 UTC⏱ Duration: 2h 17m
We are investigating elevated response times affecting users accessing Aevum News content from edge servers in our Frankfurt and Amsterdam CDN locations. The issue appears to be related to a routing anomaly within our upstream CDN provider's network. Readers in Europe may experience slower page load times (500ms–2s additional latency). Content delivery remains fully functional.
Timeline
14:23 UTC — Impact Detected
Automated monitoring systems detected elevated response times (>500ms) on EU edge nodes. Alert escalated to the infrastructure team.
14:45 UTC — Investigation
Root cause identified: a BGP routing anomaly with our CDN provider's European backbone. Engaging provider support team for resolution.
15:30 UTC — Partial Recovery
CDN provider deployed a BGP filter to correct the routing issue. Response times improving across most EU locations, though some edge nodes still show elevated latency.
16:40 UTC — Monitoring
Response times have stabilized within acceptable ranges (<200ms). Continuing to monitor for 4 more hours to confirm full resolution. No action required from readers.
🔴 Major — Resolved
Breaking News Feed Delivery Interrupted
📅 June 29, 2025 at 09:12 UTC⏱ Duration: 1h 34m
The real-time breaking news feed experienced intermittent failures between 09:12 and 10:46 UTC. This affected push notifications for breaking news alerts and the live ticker widget on the homepage. Users who subscribed to breaking news notifications may have missed alerts during this window. All missed notifications were resent once service was restored.
Timeline
09:12 UTC — Incident Start
The WebSocket service powering real-time news feed delivery began dropping connections. Breaking news push notifications failed to deliver to approximately 40% of mobile app users.
09:28 UTC — Identified
Team identified memory leak in the feed aggregation microservice causing intermittent process crashes. Rolling back to previous stable deployment.
09:55 UTC — Mitigated
Rollback completed. Feed delivery service restarted. Monitoring connection stability and notification delivery rates.
10:20 UTC — Missed Notifications Resent
All missed breaking news notifications from the incident window have been resent to affected subscribers.
10:46 UTC — Resolved
Service fully restored. All systems operational. Post-mortem analysis initiated. A fix for the memory leak will be included in the next patch release.
ℹ Info — Resolved
Scheduled CMS Database Migration
📅 June 27, 2025 at 01:00 UTC⏱ Duration: 42 minutes
As part of our ongoing infrastructure optimization, we performed a scheduled migration of the Content Management System database to a new cluster with enhanced performance characteristics. This operation resulted in brief read latency (50–100ms additional) within the CMS used by our editorial team. There was no impact to readers or public-facing services.
Timeline
01:00 UTC — Migration Started
CMS read traffic shifted to new database cluster. Editorial team notified of brief expected latency.
01:20 UTC — Data Verification
Automated integrity checks confirmed all article data, metadata, and media references migrated successfully.
01:42 UTC — Complete
Migration complete. All CMS operations normalized. New cluster showing 30% improvement in query performance.