Hourglyph
EN

Save your Claude Code limits

When is Claude Code busiest?

Hourglyph helps you save Claude Code limits by starting work in off-peak hours. A live map of sessions by hour, weekday and country, in your time zone, shows when the load peaks and which quiet hours are best for long agent runs.

Right now · in your time zone

…

Anthropic status:Checking…

messages this hour
0
messages, 24 h
0
tokens, 24 h
0
sessions, 24 h
0

Load by hour and weekday

Messages you send to Claude — the closest measure of load.

Claude Code activity by weekday and hour (UTC)
Day01234567891011121314151617181920212223
Mon
Tue
Wed
Thu
Fri
Sat
Sun
UTC · All time

Colour shows activity in each hour — messages, tokens or sessions, whichever is selected — relative to the busiest hour of the week; the outlined cell is the current hour. Switch views to see totals by hour of day, by weekday, or a world map of where check-ins come from. Need a specific zone? All time zones.

What the data says

  • Weekday peak8 PM–11 PM
  • Quietest hours2 AM–5 AM
  • Busiest dayWednesday
  • Quietest daySunday
  • Weekend share9%

Based on community data (1,324 messages), 3-hour windows, in UTC.

Incidents per Anthropic’s status page

  • Most incidents1 PM–4 PM
  • Fewest incidents2 AM–5 AM
  • Most incident-prone dayThursday

171 incident hours with an open incident for Claude, the API or Claude Code, in UTC. Source: status.claude.com, synced hourly.

Anthropic’s stated peak window

12 PM–6 PM

Weekdays, 5–11 AM Pacific, shown in UTC. In March 2026 Anthropic said 5-hour limits drain faster during these hours; on May 6, 2026 that reduction was removed for Claude Code on Pro and Max, but it remains the busiest part of the day.

How Hourglyph helps you save limits

Limits depend on the clock

In March 2026 Anthropic made 5-hour limits drain faster during the weekday peak. On May 6, 2026 that was lifted only for Claude Code on Pro and Max. The map shows when the peak is, so you don’t land in it by accident. More on limits.

Fewer wasted re-runs

Peak hours bring slower replies and overloaded errors. An interrupted agent task has to be started again, and your limit goes on the retry instead of the work.

All ways to save your limits →

How it works

1. Hooks record sessions, messages and tokens

Three hooks in ~/.claude/settings.json anonymously record session starts, every message you send and the tokens used per turn — so load inside long sessions shows up too. The server stamps the hour and weekday itself. Set it up.

2. The map aggregates everyone

Only the event type, weekday, UTC hour, country (detected by the network) and token counts are stored — no text, code or IPs. The aggregates are open: download JSON/CSV.

Peak hours in your time zone

Guides