- Joined
- Aug 23, 2009
- Messages
- 21,870
- Reaction score
- 39,609
All,
We became aware of an access issue yesterday (6/30) where under specific conditions would cause entire network segments to be blocked from access TAG. (For tech people: Class A, B IPv4 networks.)
The root cause is a misconfiguration of a firewall device with rules that were too stringent. These rules had been approved and in production since our bot problems during 2015.
On 6/30/2016, we began relaxing some of the restrictions which enabled affected users to begin seeing TAG again.
Most notably - Some travellers to Japan using a data SIM card were heavily impacted unbeknownst to us until we got a tip about the issue by a member.
Now, we will be evaluating our access monitoring related to the firewall configurations currently in place.
Please note that the adaptive rules are still being enforced and we will still continue block troubled networks if issues continue to arise.
Apologies for the inconvenience caused for those whom were trying to legitimately use TAG.
We became aware of an access issue yesterday (6/30) where under specific conditions would cause entire network segments to be blocked from access TAG. (For tech people: Class A, B IPv4 networks.)
The root cause is a misconfiguration of a firewall device with rules that were too stringent. These rules had been approved and in production since our bot problems during 2015.
On 6/30/2016, we began relaxing some of the restrictions which enabled affected users to begin seeing TAG again.
Most notably - Some travellers to Japan using a data SIM card were heavily impacted unbeknownst to us until we got a tip about the issue by a member.
Now, we will be evaluating our access monitoring related to the firewall configurations currently in place.
Please note that the adaptive rules are still being enforced and we will still continue block troubled networks if issues continue to arise.
Apologies for the inconvenience caused for those whom were trying to legitimately use TAG.