If your BGP route is not propagating, start with the exact IPv4 prefix and the ASN originating it. An established session can still carry a route that your upstream filters or never exports.
A missing Internet Routing Registry (IRR) route object, an outdated AS-SET or a filter built before your last update can all produce the same symptom. These checks are especially useful when activating leased IPv4 space or changing providers.
Check three things first. Is your router advertising the prefix? Does your upstream accept it? Can independent networks see the expected origin ASN?
A working BGP session proves that two routers can exchange routing information. It does not prove that every advertised prefix is accepted by the receiving network or propagated further.
Your upstream provider may build an allowed-prefix list from IRR records. If the advertised prefix and Origin ASN do not match that list, the provider can reject the route while leaving the session up. Even an accepted route may have limited visibility farther downstream, where different operators apply different policies.
The Internet Routing Registry is a distributed collection of databases where network operators document routing intentions. A route object records a relationship between an IPv4 prefix and its expected Origin ASN; route6 is used for IPv6. An AS-SET groups autonomous systems and may help providers generate customer-cone prefix filters.
A generic template showing the key fields of a route object:
route: <IPv4-prefix>
origin: <Origin-ASN>
source: <IRR-database>
These placeholders are not a real registry entry. Creating an IRR object does not itself advertise a BGP route or guarantee acceptance. It gives operators input they may use in their filtering policies.
If no suitable route object exists in the IRR sources your upstream trusts, the prefix may be absent from its permitted-prefix list. Verify the expected object and ask the party with authorization to create or correct it.
This can happen when switching providers, changing ASN, moving a data center or handing a leased block to a new tenant. Verify the actual Origin ASN and update the appropriate routing records with authorization from the resource holder.
Previous holders or tenants may leave stale routing information behind. Conflicting objects do not always prevent routing, but they can produce inconsistent filter results across providers. Review records in the relevant IRRs and remove obsolete objects where authorized.
If the required ASN is missing from an AS-SET used by your upstream, automatically generated prefix lists may omit routes. Confirm which AS-SET the provider uses and whether its membership reflects the intended routing arrangement.
IRR is not one database. RIPE, ARIN, APNIC, AFRINIC, RADb and other sources are not necessarily consumed in the same way by each network. Ask your upstream which sources it trusts and when it rebuilds filters.
Start with your exact IPv4 prefix and the Origin ASN you intend to advertise:
| Field | Expected | What a mismatch can mean |
|---|---|---|
| route | Your announced IPv4 prefix | Wrong or absent allowed prefix |
| origin | Your actual Origin ASN | Filter may reject the announcement |
| source | IRR your upstream uses | Record may not be considered |
| AS-SET membership | ASN included if required | Derived filter may omit your route |
The process depends on how frequently upstream providers synchronize registry data, update prefix filters, and apply changes to their routing policies.
A registry update and an upstream filter refresh are separate events. Ask your upstream which IRR source it last imported, when its next rebuild is due and whether it can refresh the filter manually before your cutover.
Different networks have different filtering policies, data sources and refresh schedules. A prefix may be visible in one part of the Internet but rejected by another. Partial reachability is therefore a useful symptom, not proof that your BGP configuration is correct everywhere.
Compare the origin ASN and AS paths from several collectors. Ask your upstream whether it accepted the prefix and exported it to the affected peer. If the route is visible but users still cannot reach the service, check packet forwarding and the return path as well.
The IP resource holder and the organization originating the leased prefix may be different parties. Before turning on a leased block, agree on which ASN will announce it and who can create, edit or delete the required IRR objects and RPKI ROAs.
Confirm these items with the lessor and your upstream: authorized use of the prefix, correct route object, Origin ASN, AS-SET membership if used, ROA alignment, provider IRR sources, and responsibility for cleanup when the lease ends.
| Mechanism | Main question | Typical data |
|---|---|---|
| IRR | Does the route match published routing-policy information used for filtering? | route, route6, AS-SET |
| RPKI | Is this Origin ASN cryptographically authorized for the prefix and length? | ROA / validated prefix-origin authorization |
A route may have correct IRR records but still be RPKI Invalid, or be RPKI Valid but missing from a provider's IRR-derived prefix list. Check both. Neither mechanism independently guarantees worldwide reachability.
Lease IPv4 space for your next deployment
Compare available IPv4 blocks on the InterLIR Marketplace. Before activation, confirm who will maintain the route object and authorize your origin ASN.
Vladislava Shadrina
Customer Account Manager
Live chat is provided by Intercom and is loaded only after you enable it. You can also contact us without enabling the chat.