Is Frontify Down?
- Frontify's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 206 ms
Right now
The verdict is the worse of these two. How we decide
Frontify's status page
status.frontify.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Frontify Website | Operational |
| Intercom Web Messenger | Operational |
| Intercom Intercom Web Application | Operational |
| Pusher API | Operational |
FlareWarden checks
frontify.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 206 ms
- Checked
By region
- Amsterdam reachable, 101 ms
- Chicago reachable, 220 ms
- London reachable, 156 ms
- San Jose reachable, 206 ms
- Singapore reachable, 347 ms
- Sydney reachable, 249 ms
- Tokyo reachable, 144 ms
- Toronto reachable, 225 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 37 ms | 2 ms | 8 ms | 88 ms |
| Chicago | 165 ms | 2 ms | 11 ms | 210 ms |
| London | 76 ms | 3 ms | 15 ms | 141 ms |
| San Jose | 131 ms | 3 ms | 14 ms | 193 ms |
| Singapore | 288 ms | 2 ms | 13 ms | 336 ms |
| Sydney | 209 ms | 1 ms | 7 ms | 237 ms |
| Tokyo | 108 ms | 1 ms | 8 ms | 137 ms |
| Toronto | 133 ms | 1 ms | 17 ms | 212 ms |
History
Incidents Frontify reported
Since Nov 4, 2 days · from status.frontify.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Frontify website availability
Measured by FlareWarden · frontify.com
- Last 7 days
- —
- Last 30 days
- —
- Last 90 days
- —
- Avg response, 30 days
- —
Last 30 days
Measured by FlareWarden's own checks of frontify.com from multiple regions every 6 hours. Frontify's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Frontify does
Frontify is a brand management platform. Brand teams and their agencies keep brand guidelines, digital assets and templates in it, and everyone producing content finds, shares and builds on-brand material from one place. Its status page lists the website, the Enterprise application in Frontify's US and EU data centers, the Self-Service application in the US, and rows for Intercom and the Pusher API.
What an outage looks like
Incidents usually mean slow uploads, Library pages loading slowly, or new assets not appearing, in one data center at a time. On July 24, 2026 asset uploads and Library loading slowed in the EU data center for about two hours. During the October 20, 2025 AWS outage, image processing and search slowed for Self-Service customers in the US, and newly uploaded assets could fail to appear.
What to do about it
Check status.frontify.com for your environment: the Enterprise application in the US and EU data centers and the Self-Service application each have their own row. If assets you uploaded during an incident are missing, look again after it closes before uploading them twice. Frontify asks customers who still see problems after an incident is resolved to contact support@frontify.com.
Is it down for everyone, or just you?
If this page says Frontify is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Frontify outage FAQ
Is Frontify down for everyone or only my data center?
Does an AWS outage affect Frontify?
Why don't my newly uploaded assets show up in the library?
How long do Frontify outages usually last?
How we measure this
- We request Frontify's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Frontify publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Frontify itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Frontify goes down
We check Frontify every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring