Travis CI · Operational
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Travis CI status

Travis CI · Atlassian Statuspage
Operational
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

No active incidents were included in this vendor report.

Maintenance

No active or upcoming maintenance was included in this vendor report.

Component health

Reported
22
Retained
22
Affected retained
0
Projection scope: complete · 22 retained of 22 reported components across 3 source groups.
Log Processing Group: Background Processing Operational
API Operational
GitHub Group: Third Party Services Operational
Web App Operational
User Sync Group: Background Processing Operational
DNSimple Name Servers Group: Third Party Services Operational
Notifications Group: Background Processing Operational
Linux and Windows Builds Group: Builds Processing Operational
IBM Z Builds Group: Builds Processing Operational
Pusher Pusher REST API Group: Third Party Services Operational
Pusher WebSocket client API Group: Third Party Services Operational
Google Cloud Platform Google Compute Engine Operational
Pusher Presence channels Group: Third Party Services Operational
GitHub API Requests Operational
Pusher Webhooks Group: Third Party Services Operational
GitHub Issues, PRs, Dashboard, Projects Operational
AWS ec2-us-east-1 Group: Third Party Services Operational
Assembla API and Merge Requests Operational
GitLab API and Pull Requests Operational
PagerDuty Notification Delivery Group: Third Party Services Operational
Showing 20 of 22 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.

Recent observed status changes and checkpoints

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Operational
HTTP 200 · 128.77 ms feed latency
Operational
HTTP 200 · 165.2 ms feed latency
Operational
HTTP 200 · 87.53 ms feed latency
Operational
HTTP 200 · 147.54 ms feed latency
Operational
HTTP 200 · 258.58 ms feed latency
Operational
HTTP 200 · 180.17 ms feed latency
Operational
HTTP 200 · 229.76 ms feed latency
Operational
HTTP 200 · 297.36 ms feed latency
Operational
HTTP 200 · 324.1 ms feed latency
Operational
HTTP 200 · 121.04 ms feed latency

Collection details

Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
266.64 ms