Skip to content
Honeybadger Docs

Data residency

View Markdown

Data residency refers to the physical location where your organization’s data is stored and processed. It’s a way to ensure that data like customer information, application logs, and business data remain within the geographical borders of a specific country or region.

Honeybadger offers two regions (US and EU) so that your organization can choose where your data is stored and processed.

United States

Section titled “United States”

Honeybadger stores your data in the US by default (Amazon’s us-east-1 region). Unless you specifically signed up for our EU region, this is where your data is located.

If you access Honeybadger via one of the following subdomains, you’re in our US region:

  • app.honeybadger.io
  • api.honeybadger.io

European Union

Section titled “European Union”

You can optionally sign up for an account in our EU region, which we operate on dedicated infrastructure in Amazon’s eu-central-1 region in Frankfurt, Germany.

Honeybadger EU accounts are purchased separately, allowing you to choose different tiers depending on your needs. The pricing and features we offer are otherwise the same across both regions.

If you access Honeybadger via one of the following subdomains, you’re in our EU region:

  • eu-app.honeybadger.io
  • eu-api.honeybadger.io

Moving an account from the US to the EU

Section titled “Moving an account from the US to the EU”

If you already have a US account and want to move to the EU region, we can copy your account’s configuration for you. Historical data does not move, so plan the switch as a cutover rather than a lift-and-shift.

What moves:

  • Projects, along with their API keys
  • Teams, team members, and their roles
  • Integrations (without their credentials)
  • Uptime sites
  • Check-ins, along with their check-in tokens
  • Project actions (rules that tag, assign, and route incoming errors)
  • Insights dashboards

What does not move:

  • Errors, notices, and deploys
  • Insights events
  • Alarms
  • Status pages
  • Source maps
  • SAML configuration
  • Billing and subscription details

Your existing US data stays where it is; it is not copied to the EU, and it is not deleted until you ask us to close the US account.

How to request a migration

Section titled “How to request a migration”
  1. Sign up for an EU account. It must be a brand new account with no projects in it, on a plan at least as large as your current US plan.
  2. Email support with the account IDs of both your US account and your new EU account, and we’ll schedule the migration with you.

What to expect afterward

Section titled “What to expect afterward”
  • Your project API keys stay the same, so you only need to point your Honeybadger clients at the EU endpoints. Most libraries have more than one region-specific setting: the JavaScript library, for example, has separate endpoint, userFeedbackEndpoint, and deployEndpoint values, and Laravel adds appEndpoint. Check your library’s configuration reference and update every one of them to its full https://eu-api.honeybadger.io or https://eu-app.honeybadger.io URL.
  • Your check-in tokens stay the same, but the check-in URLs change to eu-api.honeybadger.io. Update them wherever they’re invoked, such as in your cron jobs.
  • Every integration must be reconnected. We copy each integration’s settings, but never its credentials, so you’ll reauthorize Slack, PagerDuty, GitHub, and anything else on the EU side.
  • Everyone on your team gets a “set your password” email. Passwords and two-factor settings do not move between regions.
  • Project and dashboard URLs change, because the new account has new project IDs. Update any bookmarks or links you’ve saved.

Both regions keep accepting data for the same API keys during the switch, so you can move your applications over at your own pace. Once the EU account is working the way you expect, let us know and we’ll close the US account.