Major outage caused by DDoS at Linode Atlanta
Resolved
The DDoS seems to be resolved for now, but we'll keep an eye on it.
Sep 3, 9:27 PMResolved Sep 7, 3:22 AMMajor
Status Provider
Home
/
Status
/
Service
Operational
Clojars Status
Community repository for open source Clojure libraries.
Source
statuspage.io
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 3m ago
5
Components
0
Active incidents
0
Maintenance
100%
90d uptime
Major outage caused by DDoS at Linode Atlanta
Sep 3, 9:27 PM
Service health overview
Operational snapshot
Normalized official status-page data for incidents, maintenance, components, and history.
100%
Known uptime
1 known history days
5
Components tracked
0 outage, 0 degraded
8
Incidents indexed
0 active right now
10
Maintenance windows
0 active or scheduled
Top affected components
Components with the most recent status-page events.
API
Operational
1
Badges
Operational
1
DNSimple Name Servers
Operational
1
JAR repository
Operational
1
Site
Operational
1
90-day status history
Daily rollup
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
0
outage days
0
maintenance days
89
unknown days
Recent incidents
Official incidents
Latest outages and degradations detected from the official status page.
Upstream network outage at Linode
Resolved
Looks like we're all better now
Aug 30, 7:01 PMResolved Aug 30, 9:04 PMMajor
Clojars unavailable
Postmortem
## Summary There was approximately 25 minutes of server downtime from 2016-08-05 09:46 UTC to 2016-08-05 10:09 UTC while updating nginx. The root cause was a change in nginx default behaviour around IPv6 sockets which caused IPv4 connections to be ignored. ## Details The version of nginx installed on the server was quite old. Before upgrading, I looked through the release notes to look for changes. I copied them to a text file for easy reference if something went wrong. Nothing in the changelog looked like it would affect us (though crucially, I didn't fully understand all the mentioned changes...). I updated nginx while it was running (to prevent downtime being too long). Once the update had finished, I restarted nginx. It reloaded and everything seemed to be ok. I then realised that the old process was running, and the new version hadn't started. After killing the old process and starting the new one, clojars.org wasn't accessible. I searched for possible answers, and a change that was mentioned in the changelog came up: `ipv6only` was now set on by default for IPv6 sockets. This means that only IPv6 connections would be accepted and IPv4 would not connect. If you were connecting to Clojars over IPv6, you would have had no connectivity issues. I updated the nginx server config to turn off `ipv6only`, and service was restored. ## Learnings * When updating software, make sure that we understand all changes in the changelog, especially ones which change default behaviour. * If possible it would be good to test upgrades on a test server before applying it to the production server.
Aug 5, 9:42 AMResolved Aug 5, 10:06 AMNone
Linode network outages
Resolved
Linode issues appear to be resolved. Everything should be operational.
Apr 22, 10:18 AMResolved Apr 22, 1:26 PMMinor
Upstream network maintenance
Resolved
This incident has been resolved.
Mar 1, 11:28 PMResolved Mar 1, 11:33 PMMinor
Network issues
Resolved
It seems like everything is back to normal.
Feb 26, 3:10 AMResolved Feb 26, 3:55 AMMajor
Network issues
Resolved
Looks like it was just a temporary blip. Back to your regularly scheduled Clojure programming.
Feb 18, 7:30 AMResolved Feb 18, 7:37 AMMinor
Connectivity issues with Linode Atlanta
Resolved
It seems like everything is stable and back to normal, but we'll keep monitoring the situation.
Feb 2, 4:58 PMResolved Feb 2, 8:26 PMMajor
Recent maintenance
Maintenance windows
Scheduled and completed maintenance windows are separated from incidents.
Brief maintenance downtime
Completed
The scheduled maintenance has been completed.
Dec 8, 9:15 PMResolved Dec 8, 9:22 PMMaintenance
Reboot to update OS
Completed
The scheduled maintenance has been completed.
Oct 5, 7:45 PMResolved Oct 5, 7:54 PMMaintenance
Brief downtime to deploy new features
Completed
The scheduled maintenance has been completed.
Oct 5, 12:00 AMResolved Oct 5, 12:26 AMMaintenance
Moving to Rackspace
Completed
The migration has completed, all seems to be normal. Let us know if there are any issues.
Sep 26, 2:00 AMResolved Sep 26, 3:11 AMMaintenance
Scheduled downtime for upstream maintenance
Completed
Maintenance is complete.
Sep 7, 2:00 AMResolved Sep 7, 3:20 AMMaintenance
Scheduled maintenance to upgrade nginx
Completed
Everything seems to have gone suspiciously well. Maintenance over, but monitoring.
Aug 5, 9:00 AMResolved Aug 5, 9:12 AMMaintenance
Downtime for Linode maintenance
Completed
The scheduled maintenance has been completed.
Jul 22, 2:00 AMResolved Jul 22, 2:27 AMMajor
Site downtime to deploy new features
Completed
Maintenance is complete, site should be fully operational
Jun 21, 1:00 AMResolved Jun 21, 2:06 AMMajor
Downtime to deploy new features
Completed
Maintenance canceled - site is fully operational
Jun 13, 12:00 AMResolved Jun 13, 1:04 AMMajor
Brief downtime to install security updates and reboot
Completed
The scheduled maintenance has been completed.
Feb 19, 2:00 AMResolved Feb 19, 2:04 AMNone
About the Clojars status page integration
Uptimus tracks the official Clojars status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://clojars.statuspage.io
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Outage map preview
Regional reports can be layered on top of official provider status when user signals are available.
Clojars components
Tracked components
Showing 1 to 5 of 5 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Site clojars.org user facing site | Operational | Component | Not recorded |
JAR repository | Operational | Component | Not recorded |
API | Operational | Component | Not recorded |
Badges | Operational | Component | Not recorded |
DNSimple Name Servers | Operational | Component | Not recorded |
Get notified when Clojars changes status
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Show Clojars on your own status page
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Users also follow these services
Related status pages based on category, adapter type, and operational history.
Frequently asked questions
Is Clojars down right now?
Clojars is currently marked as Operational in Uptimus based on the latest official status page check.
How often does Uptimus check Clojars?
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
Are maintenance windows counted as incidents?
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Can I get alerts for Clojars?
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.