Home
/
Status
/
Service
Project management for GitHub with Kanban boards and automation.
Source
auto
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 31m ago
4
Components
0
Active incidents
0
Maintenance
50%
90d uptime
Web service outage
Jun 27, 7:45 AM
Normalized official status-page data for incidents, maintenance, components, and history.
50%
Known uptime
2 known history days
4
Components tracked
0 outage, 0 degraded
27
Incidents indexed
0 active right now
10
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
GitHub Webhooks
Operational
GitHub API Requests
Operational
GitHub Issues, Pull Requests, Projects
Operational
Web App
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
1
degraded days
0
outage days
0
maintenance days
88
unknown days
Latest outages and degradations detected from the official status page.
AWS Fargate changed the way containers share volumes within a task. This change in behavior caused a deployment failure along with failures on rollback. The solution required redesigning the container infrastructure to not require shared volumes
resolved
This incident has been resolved.
this incident is resolved and ongoing monitoring is in place
This incident has been resolved; We'll continue to monitor to ensure all clients are back to normal
Github resolved their outage as of 5:01 UTC
This incident has been resolved.
This incident has been resolved.
The index issues have been resolved
GitHub seems to be running smoothly again
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.
Database maintenance is complete and we're back online.
The scheduled maintenance has been completed.
Uptimus tracks the official Codetree status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.codetree.com
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.
Showing 1 to 4 of 4 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Web App | Operational | Component | Not recorded |
GitHub API Requests | Operational | Component | Not recorded |
GitHub Webhooks | Operational | Component | 6/15/2026 |
GitHub Issues, Pull Requests, Projects | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Codetree 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.
