Hello Mixpanel Dev list,
This is a critical update for users with infrastructure restricting certain IP addresses (aka egress filtering) when writing data to Mixpanel. This is an uncommon situation, however, please read the next section to prevent possible service disruption.
Will this affect me?
Data sent from client-side libraries (JavaScript, iOS, Android, Blackberry, etc) will be totally unaffected – you don't need to continue reading.
The vast majority of server-side libraries (Python, Ruby, PHP, custom backend libraries, or via a proxy server) will also be unaffected. Nonetheless, users sending data from server-side libraries should read the next section to be certain.
This change will only impact Mixpanel users who have implemented backend tracking from servers behind firewalls that restrict outgoing traffic by IP address (commonly called egress filtering) without using DNS to determine the ranges (i.e. you restrict outgoing writes to hard-coded IP addresses or ranges).
What is happening?
Mixpanel's Engineering team will bring new IP addresses online to support our services around the world. The changes are exclusive to the write-only api (
api.mixpanel.com). This means that event tracking or people calls to
api.mixpanel.com will soon resolve to additional IP addresses. No IP addresses are being removed at this time.
Note: this will not effect read-api requests to data export (mixpanel.com/api/2.0) or raw data export (data.mixpanel.com).
When is it happening?
Changes are scheduled to go live on or after Monday, February 2nd at 12:00pm Pacific time (2015-02-02 20:00 UTC).
What should I do if I am egress filtering?
Email
sup...@mixpanel.com as soon as possible to discuss a solution that will prevent service interruption if you use
egress filtering (allow only specified IP addresses or ranges for IP addresses) for writing data to Mixpanel. If you're using a server-side library and are unsure, please email
sup...@mixpanel.com and CC your engineering team.
Thanks for your time and attention,
Mixpanel