PostlyResearchPublishing times · October 2026 findings
Publishing times: the busiest hour is not a growth prescription
A complete September UTC distribution provides operational context for scheduling and a clearer basis for audience-local timing tests.
Source: Postly Research. Anonymized retained publishing data: 72,883 documents inspected; 47,388 posts with verified publications; 165,158 deduplicated destination deliveries; 3,645 destination accounts. Observation cutoff: 2026-10-04 22:35:49 UTC.
Download this complete report ↓Publishing times
Publishing times: the busiest hour is not a growth prescription
A complete September UTC distribution provides operational context for scheduling and a clearer basis for audience-local timing tests.
September 1-30, 2026 (UTC).
The finding
The largest published hourly bucket is 13:00 UTC, with 6,191 deliveries; the smallest is 10:00 UTC, with 2,876. Activity is distributed across every UTC hour in the published table. This describes a global publishing workflow; it does not measure when audiences were online or most responsive.
Deduplicated September 2026 publications by UTC hour, across platforms. Account counts overlap between hours.
| Observed group | September deliveries | Accounts |
|---|---|---|
| 13:00 UTC | 6,191 | 568 |
| 14:00 UTC | 5,891 | 594 |
| 12:00 UTC | 5,658 | 463 |
| 17:00 UTC | 5,607 | 459 |
| 15:00 UTC | 5,415 | 558 |
| 18:00 UTC | 5,237 | 499 |
| 16:00 UTC | 4,976 | 517 |
| 11:00 UTC | 4,974 | 419 |
| 09:00 UTC | 4,563 | 467 |
| 02:00 UTC | 4,546 | 358 |
| 05:00 UTC | 4,542 | 493 |
| 23:00 UTC | 4,432 | 336 |
| 19:00 UTC | 4,420 | 435 |
| 03:00 UTC | 4,321 | 309 |
| 06:00 UTC | 4,117 | 567 |
| 08:00 UTC | 4,078 | 677 |
| 00:00 UTC | 4,030 | 358 |
| 22:00 UTC | 3,990 | 357 |
| 04:00 UTC | 3,871 | 407 |
| 20:00 UTC | 3,827 | 357 |
| 01:00 UTC | 3,741 | 311 |
| 07:00 UTC | 3,653 | 547 |
| 21:00 UTC | 3,557 | 312 |
| 10:00 UTC | 2,876 | 406 |
At least 30 accounts and 100 observations per displayed group. Account counts overlap. Small groups are withheld; absence from this table does not mean zero usage.
What this means for scheduling
A universal best-time recommendation would confuse publisher behaviour with audience response. The same UTC hour corresponds to different local hours across regions, and the aggregate also mixes platforms and content. Use the observed spread to plan operational coverage and verification. Audience-local experiments need a narrower comparison than this global distribution.
Recommended actions
Record the audience timezone alongside every timing test. Compare two practical local-time windows on the same platform with similar content and a fixed observation age. Include a response or conversion measure rather than only publication success. Keep enough time after publishing to monitor responses, and revisit the schedule when audience geography or daylight-saving time changes.
How to use the full table
Each row is an observed publication hour, not a recommended time slot. September is a completed month, avoiding the partial October window in the retained census. There is no hourly engagement or conversion denominator in this study, so a high-volume hour cannot be called more effective and a low-volume hour cannot be called an opportunity without an outcome test.
Source and counting rules
The census reads retained Postly production records in bounded batches from a database secondary. Receipts require platform, destination account, publication identifier and timestamp. TikTok also requires confirmed success. Repeated provider identifiers are counted once per destination. This is a live retained-data census, not a random sample or an atomic snapshot. Deleted records and publishing outside Postly are absent. Small groups are withheld: every displayed row requires at least 30 destination accounts and 100 observations. Accounts are not necessarily independent businesses; their counts overlap between rows.
Citation: Postly Research, Publishing times: the busiest hour is not a growth prescription, October 2026.