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 <e...@globalvision.net
<mailto:e...@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-boun...@nanog.org
<mailto:nanog-boun...@nanog.org> on behalf of
mike.l...@gmail.com <mailto:mike.l...@gmail.com>"
<nanog-boun...@nanog.org <mailto:nanog-boun...@nanog.org> on
behalf of mike.l...@gmail.com <mailto:mike.l...@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
<e...@globalvision.net <mailto:e...@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.man...@charter.com
<mailto:charles.man...@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.
>
