They don't care at all.
They are not interested in helping in any way.
All four times I contacted they were extremely rude.
On 2/8/2018 12:11 PM, Jason Canady wrote:
Has anyone found a resolution to this? Our network has been blocked
and I had a customer mention it to me the other day, so I
Has anyone found a resolution to this? Our network has been blocked and
I had a customer mention it to me the other day, so I would like to get
it resolved.
Thank you!
Best Regards,
--
Jason Canady
Unlimited Net, LLC
Responsive, Reliable, Secure
On 2/7/17 12:05 PM, Manser, Charles J
All,
Thank you for the suggestions. All (3) of the e-mail addresses associated with
their ARIN records bounced back.
Remote Server returned '< #5.7.133 smtp;550 5.7.133
RESOLVER.RST.SenderNotAuthenticatedForGroup; authentication required; Delivery
restriction check failed because the
On 2/6/17 8: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
On Mon, Feb 06, 2017 at 12:39:44PM -0500, Ken Chase wrote:
> Seems to me this random prefix-based blocking by major sites,
> then let's-use-nanog-to-fix-it, is not a great methodology.
You're correct. It's not.
> What more 'official' and formalized mechanisms can we use?
RFC 2142 stipulates
Seems to me this random prefix-based blocking by major sites,
then let's-use-nanog-to-fix-it, is not a great methodology.
I block whole /18s and such to deal with .cn/.ru botnets too, but luckily my
cxs' cxs are mostly North American, few complaints yet. Sledgehammer style -
indelicate.
Is
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
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 wrote:
> So their policy says, if an ISP has one scalper, we'll block their entire
> subnet and not tell them why?
>
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
Another way to get on their block list is to have a lot of users behind a
single NAT or proxy IP address. In my experience they blocked single IPs.
The first time it was easy to explain that there were 30,000 users behind
the single address and get the block cleared. After that it became more
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
Yup, i have a /22 that has the same problem. Support is useless...
> On Feb 6, 2017, at 08:35, Ethan E. Dee 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
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 (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?
No Issues from AS26269 via HE NYC (AS6939)
*Ben Hatton*
Network Engineer
Haefele TV Inc.
d:(607)589-8000
bhat...@htva.net
www.htva.net
On Mon, Feb 6, 2017 at 10:42 AM, Christian Kildau wrote:
> 403 forbidden from as12306 via level3.
>
> On Mon, Feb 6, 2017 at 2:04 PM,
403 forbidden from as12306 via level3.
On Mon, Feb 6, 2017 at 2:04 PM, Manser, Charles J <
charles.man...@charter.com> wrote:
> List,
>
> 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
Can get to them from Equinox connected Peer.
- Original Message -
From: "TR Shaw" <ts...@oitc.com>
To: "Charles J Manser" <charles.man...@charter.com>
Cc: nanog@nanog.org
Sent: Monday, February 6, 2017 10:26:50 AM
Subject: Re: ticketmaster.com 403 Forb
Can get to them fine from Florida via level3.
Tom’
> On Feb 6, 2017, at 8:04 AM, Manser, Charles J
> wrote:
>
> List,
>
> It seems that browsing to ticketmaster.com or any of the associated IP
> addresses results in a 403 Forbidden for our customers today. Is
List,
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?
If anyone from Ticketmaster could reach out to me off-list, it would be helpful.
Charles Manser | Principal Engineer I,
19 matches
Mail list logo