Info

Several networks announce this prefix

The short version

If you run one of them, check with the others that the overlap is planned; an unplanned one can be a route leak or hijack.

What it means

More than one network originates the same prefix in the global routing table. Normally one AS number announces a prefix; here two or more do, so routers elsewhere pick one of them depending on where they sit. This is called a multiple-origin announcement.

Why it matters

Planned overlaps are common. Anycast services announce the same prefix from several networks on purpose, and a company moving between providers announces from both for a while. An overlap nobody planned is different: some traffic for your addresses goes to a network that doesn't run your servers. That can be a configuration mistake at another network, or someone deliberately announcing addresses that aren't theirs.

How to fix it

  1. Note the AS numbers the result lists and look each one up with the ASN lookup.
  2. If every origin is a network you or your provider use (an old and a new provider, or an anycast partner), confirm with them that the overlap is planned and when it should end.
  3. If an origin is unknown to you, contact your provider's network team at once with the prefix and the AS number. They can contact the other network and its upstream providers.
  4. Publish route origin authorizations (RPKI) for your prefixes with your regional registry, so networks that validate routes ignore announcements from the wrong origin.

Check it worked

Look up an address in the prefix again after the change. The routing table refreshes once a day, so the result should show a single origin within a day.