ticketmaster.com 403 Forbidden
matlockken at gmail.com
Mon Feb 6 17:22:42 UTC 2017
Honestly, I'm surprised they don't try and charge a 'convenience fee' while
implementing the block! ;-)
On Mon, Feb 6, 2017 at 10:19 AM, Ethan E. Dee <edee at globalvision.net> wrote:
> So their policy says, if an ISP has one scalper, we'll block their entire
> subnet and not tell them why?
> On 02/06/2017 11:49 AM, Suresh Ramasubramanian wrote:
>> My guess is you have or had sometime in the long distant past a scalper
>> operating on your network, using automated ticket purchase bots.
>> If you still have that scalper around, you might want to turf him. If
>> he’s ancient history, saying so might induce them to remove the block.
>> On 06/02/17, 8:45 AM, "nanog-bounces at nanog.org on behalf of
>> mike.lyon at gmail.com" <nanog-bounces at nanog.org on behalf of
>> mike.lyon at gmail.com> wrote:
>> Yup, i have a /22 that has the same problem. Support is useless...
>> > On Feb 6, 2017, at 08:35, Ethan E. Dee <edee at globalvision.net>
>> > It gives me a Forbidden error.
>> > It has for over a year.
>> > There support says they are not allowed to me why by their policy.
>> > it is across an entire /19.
>> > I gave up after the fifth time and encourage the customers to call
>> them individually.
>> >> On 02/06/2017 11:09 AM, Niels Bakker wrote:
>> >> * Charles.Manser at charter.com (Manser, Charles J) [Mon 06 Feb
>> 2017, 16:21 CET]:
>> >>> It seems that browsing to ticketmaster.com or any of the
>> associated IP addresses results in a 403 Forbidden for our customers today.
>> Is anyone else having this issue?
>> >> http://help.ticketmaster.com/why-am-i-getting-a-blocked-forb
>> >> -- Niels.
More information about the NANOG