[EMAIL PROTECTED] wrote:
You appear to be excessively deaggregating your space. Perhaps they
are doing the responsible thing by filtering it?
I had a /20 from which BT was unreachable, and a /24 working just fine,
so this seems doubtful, unless they are doing it to be spiteful and
punitive alone
> Mike wrote:
> >
> > We're receiving multiple complaints about problems reaching anything
> > @bt. Is anyone else experiencing this?
>
> GrrrThree days later, BT is now telling their customers that
> somehow, this is our fault. I find it rather odd that everyone in the
> world can reach
On Thu, 19 Jun 2003, Mike wrote:
> I have sent mail to every address @BT that looks like it might possess
> clue, to no avail. This is a general plea for help- if anyone has an
> idea of how I might resolve this, I would be very grateful...
Point the customer at www.traceroute.org?
HTH,
Ric
BT operate 2856 in the UK, and 5400 internationally
5400 used to be concert which was a BT/ATT venture which is now solely run by BT
under their brand - hence I guess why the msg on concert.net
Email contact sent offlist..
Steve
On Thu, 19 Jun 2003, Mike wrote:
>
> Mike wrote:
> >
> > We
Mike wrote:
I have sent mail to every address @BT that looks like it might possess
clue, to no avail. This is a general plea for help- if anyone has an
idea of how I might resolve this, I would be very grateful...
On a hunch, I shut down one of our peering sessions which was passing
our routes
Mike wrote:
We're receiving multiple complaints about problems reaching anything
@bt. Is anyone else experiencing this?
GrrrThree days later, BT is now telling their customers that
somehow, this is our fault. I find it rather odd that everyone in the
world can reach us, *except* BT customers
Yes, it appears they had problems:
Power failure leads to BTo blackout
By Tim Richardson
Posted: 17/06/2003 at 11:46 GMT
http://theregister.com/content/22/31248.html
We're receiving multiple complaints about problems reaching anything
@bt. Is anyone else experiencing this?
I.E. e-mails to @btopenworld and also @btinternet.com are bouncing. The
root cause seems that we are unable to resolve anything within bt.com et
al. For whatever reason, this is affecting
