Mike wrote:
>
> We're receiving multiple complaints about problems reaching anything
> @bt. Is anyone else experiencing this?
Grrr....Three 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, yet it is our fault.
You appear to be excessively deaggregating your space. Perhaps they
are doing the responsible thing by filtering it?
As announced, 13345 has 92 prefixes originated. After aggregation,
there are 44 prefixes. There appear to be a couple of holes which you aren't
announcing, which would further reduce this to 38 (after aggregation.)
The space from the "Colorado Internet Cooperative Association" seems to
be somewhat haphazard leading to the bulk of the remainder, and they
aren't originating 207.174.0.0/16 at all, which may lead to issues.
In this day and age of many people not doing the right thing, it is
likely that one only see's the effects when looking at someone actually
doing the right thing.
I'ld suggest cleaning up your announcements and seeing if the problem
persists. If nothing else, you become a part of the solution.
bdragon@gweep.net 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.
I say "had" because we have since withdrawn almost all announcements that AS7018 was learning from AS19694 and temporarily "fixed" the problem. It still exists, and it is clear now that the problem lies somewhere between AS7018 and AS2856. AS7018 says that my traceroutes are "confusing" to them, so I have pretty much given up hope of ever seeing a resolution to this.
As announced, 13345 has 92 prefixes originated. After aggregation,
there are 44 prefixes.
Policy for most of those were set prior to my involvement with BGP here. I have managed to prevent the (otherwise forgone) deaggregation of 204.188.96.0/20 and 199.45.236.0/22 since my involvement at this level. I am also working to prepare an application for PI space from ARIN and the end result will be to reduce our total # of prefixes. Due to topology, aggregation of the remainder at this time would require several hundred clients to renumber immediately.
Yes, I know this sucks. Yes, I am working towards a solution. No, it isn't going to happen tomorrow. Yes, I feel the pain every time I look at what we advertise.
Mike