Deaggregating for emergency purposes

> > The point was calling up the upstream of the AS who is generating bogus
> > routes. The upstream of the caller is not at all involved.
> >
> But the upstream of the caller is involved. They passed
> the route(s) on, no?
> --bill

Not necessarily, I could be the victim of a leak calling up
an ISP to report it. Or some bored person connected to
route-server.* constantly checking prefixes.

  you either generated the bogus route yourself or
  you heard it from one of your direct neighbors.

  there is no other way for you to hear the route.
  Now you can -look- for what might be bogons (from your
  perspective) in other places in the net (route-server.*)
  or some random LG. But just because a route is there
  does not mean it shows up on your border. And routes
  that show up in those places are "nominally" interesting
  only from the perspective of "...are my routes propogating..."

  If there IS a legit.bogon that shows up on your border,
  then the -only- people who can do anything about it are:

    ) yourself. *
    ) your peer.
  (*) or you can contract with me at the usual and customary
      rates to config your routers for you.
  It may take both of you to provide the types of "corrective
  lenses) to give you the view you think you want, but it is
  an affrontery to "jump over" your providers to pester other
  ISPs that you have no business pestering. The routes they
  exchange among themselves is their business.