Skip to main content
Granicus logo

Is Granicus Down?

No — Granicus is up

Reachable from all 8 checked regions

Average response time: 91ms

Last checked · checks run every 6 hours

Official status page: https://status.granicus.com

Granicus uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
137ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 14 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

14-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: no data
Sep 26: no data
Sep 27: no data
Sep 28: no data
Sep 29: no data
Sep 30: 100.00% uptime, 14 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad
85ms
DNS 27ms TCP 6ms TLS 11ms TTFB 63ms
jnb
50ms
DNS 16ms TCP 0ms TLS 9ms TTFB 44ms
lax
60ms
DNS 36ms TCP 2ms TLS 6ms TTFB 53ms
lhr
64ms
DNS 37ms TCP 1ms TLS 7ms TTFB 58ms
nrt
107ms
DNS 86ms TCP 1ms TLS 6ms TTFB 101ms
ord
72ms
DNS 57ms TCP 1ms TLS 4ms TTFB 68ms
sin
168ms
DNS 153ms TCP 0ms TLS 5ms TTFB 164ms
sjc
123ms
DNS 102ms TCP 1ms TLS 5ms TTFB 117ms

What Granicus does

Granicus sells software to government, and says more than 7,000 government organizations use it. Products include govDelivery for resident email and text alerts, govMeetings tools such as Legistar, Peak, MediaManager and Swagit for agendas and meeting video, govAccess Vision and OpenCities for government websites, and govService tools such as GovQA, SmartGov and OpenForms. Its status page also covers Simpleview products and Indigov CRMs.

What an outage looks like

Residents see a city or county website that will not load or keeps dropping out, a council meeting live stream that will not play, or agendas that open with 'This document has been removed'. Staff see Legistar slow or freezing, Peak agenda packets stuck generating, 504 Gateway Timeout errors in the Swagit admin portal, or Communications Cloud logins stalled because the voice-call two-factor code never arrives.

What to do about it

Check status.granicus.com and find the product, not just the family: govMeetings alone has 12 rows, from Legistar to Swagit, and EngagementHQ is split by region. The page offers email, SMS and RSS alerts. Staff open cases through the Support Portal at support.granicus.com. Residents with a meeting, permit or website problem should contact their agency, because Granicus subscriber help only handles govDelivery email and text subscriptions.

Is it down for everyone, or just you?

If this page says Granicus 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.

Test it yourself

Related services

Zoom
Zoom
ServiceNow
ServiceNow
Salesforce
Salesforce
SendGrid (Twilio)
SendGrid (Twilio)

Granicus outage FAQ

Is Granicus down for everyone or just me?
Almost never for everyone, because Granicus incidents usually hit one product. The status page has 56 rows across govDelivery, govMeetings, govAccess, govRecords, govService, Simpleview and Indigov, and some are regional, with EngagementHQ split into US, Canada, UK, Europe and ANZ. If your product's row is green, the problem may be limited to your agency's site or account, so open a support case.
Why won't a council meeting live stream play?
Check the Swagit and MediaManager rows on the status page first, then try another browser. Past Swagit incidents have hit only some browsers: live streams failed in Chrome and Edge while Firefox and Safari worked, and recorded meetings were unaffected. When a stream does not auto-play, clicking the video has started it. If the streaming rows are green and no browser works, contact the agency holding the meeting.
Does a Granicus outage stop govDelivery emails?
Not always, because sending and reporting fail separately. In September 2026 an analytics fault left open and click data stale in dashboards while Granicus said core messaging remained available. The same month, voice-call two-factor codes for Communications Cloud stopped arriving, but SMS-based two-factor codes kept working throughout. Communications Cloud and the Targeted Messaging Service have their own rows on the status page.
Why won't a Legistar or Peak agenda open?
Usually a govMeetings incident rather than a missing agenda. Legistar, Peak, InSite and the other meeting tools each have a row under govMeetings on the status page, so check the one your agency uses. Granicus has advised clearing the browser cache and fully restarting the browser, or trying Firefox, during agenda display faults, and asked customers to allow extra time before retrying slow Peak packets, because queued requests clear as processing returns to normal.
Who should residents contact about a Granicus problem?
Contact the city, county or agency that runs the service, not Granicus. Granicus's subscriber help site says it helps with email subscriptions and sends agency-related questions back to the agency. Government staff with a Granicus account open cases through the Support Portal at support.granicus.com, and Granicus incident notices point to that portal for anything not covered on status.granicus.com.

How we measure this

  • We request Granicus's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the 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 Granicus publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Granicus goes down

This page refreshes every 6 hours. 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
Free plan available No credit card required