GitHub outage on April 23, 2026

Read more >

Introducing StatusGator’s Accessibility Conformance Report (VPAT)

Read more >

StatusGator logo
Schedule a Demo
StatusGator logo
Use cases

IT Teams

Stay informed of outages and reduce tickets

DevOps

One status page for all your providers

Features designed specifically for K12

Advanced features designed for enterprise

Impress clients with proactive monitoring

Analyze and compare peer performance

Monitor dependencies to prevent revenue loss

Create and manage custom status pages for your product

Features

Status page

A status page with service, website, and custom monitors built-in

Status aggregation

Aggregate the status of all vendors to a single page

Monitor all your cloud services from a single dashboard

Monitor your website with uptime monitoring built-in

Monitor network connectivity

Control the status of custom monitors manually with incidents

Get notified of disruptions before they become public

Pricing

Business

From startup to enterprise and everything in between

Education

Special plans and discounts for K12 and higher ed

Integrations

Incident Management

Better Uptime
FireHydrant
Opsgenie
PagerDuty

Notifications

Private Status

AT&T status
AWS status
Azure status
Microsoft 365 status
Zendesk status

Status Pages

Atlassian Statuspage
StatusHub

Advanced

Sign In Sign Up

Improve Heroku Geolocation Performance With the GEOLITE2 Buildpack

Recently, we began using IP geolocation within StatusGator to learn where are users are located. We are happy to say that it’s working out well.  We hoped to use these insights to tune our marketing. To that end, we added the Ahoy gem to help collect information related to how our advertising campaigns are going.  The Ahoy gem  also uses the geolocation gem to look up IP addresses.  This significantly increased the number of IP geolocation lookups.  The ahoy readme suggested using the geolite2 city database in order to keep lookups local. No HTTP requests to an external services are required, as lookups use a local database.  This improves performance and prevents us from being subject to API call limits.  One problem is that the database needs to be local to the Rails app, which requires a bit of configuration tweaking when deployed to Heroku.  We created a very basic Heroku buildpack which will download the geolite2 city database into the Ruby on Rails tmp folder.

The performance gains from this have been noticeable, as our background queues do not fill up with HTTP request jobs. The accuracy is certainly good enough for our needs, pinpointing users and visitors to the approximate city from which they are visiting StatusGator.

Share this

Photo of author

Andy Libby

Andrew Libby is a veteran Ruby developer and technologist with over 25 years of experience; Andy is co-founder of StatusGator and leads engineering at Nimble Industries.