[193582] in North American Network Operators' Group
Re: ticketmaster.com 403 Forbidden
daemon@ATHENA.MIT.EDU (Ethan E. Dee)
Mon Feb 6 12:27:55 2017
X-Original-To: nanog@nanog.org
X-Globalvision-MailScanner-EFA-From: edee@globalvision.net
From: "Ethan E. Dee" <edee@globalvision.net>
To: Ken Matlock <matlockken@gmail.com>
Date: Mon, 6 Feb 2017 12:24:30 -0500
In-Reply-To: <CAF-Wqd4ag06O7WM=kEEkMjSdSa_tRmbwaxNO0hYK+Tw=cwOQ1A@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>, Niels Bakker <niels=nanog@bakker.net>
Errors-To: nanog-bounces@nanog.org
I'm interested to see if any one has beat this.
On 02/06/2017 12:22 PM, Ken Matlock wrote:
> Honestly, I'm surprised they don't try and charge a 'convenience fee'
> while implementing the block! ;-)
>
> Ken
>
> On Mon, Feb 6, 2017 at 10:19 AM, Ethan E. Dee <edee@globalvision.net
> <mailto:edee@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.
>
> --srs
>
> On 06/02/17, 8:45 AM, "nanog-bounces@nanog.org
> <mailto:nanog-bounces@nanog.org> on behalf of
> mike.lyon@gmail.com <mailto:mike.lyon@gmail.com>"
> <nanog-bounces@nanog.org <mailto:nanog-bounces@nanog.org> on
> behalf of mike.lyon@gmail.com <mailto:mike.lyon@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@globalvision.net <mailto:edee@globalvision.net>> wrote:
> >
> > 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@charter.com
> <mailto:Charles.Manser@charter.com> (Manser, Charles J) [Mon
> 06 Feb 2017, 16:21 CET]:
> >>> It seems that browsing to ticketmaster.com
> <http://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-forbidden-or-403-error-message/
> <http://help.ticketmaster.com/why-am-i-getting-a-blocked-forbidden-or-403-error-message/>
> >>
> >>
> >> -- Niels.
> >
>
>
>
>
