bgunderlay bgunderlay bgunderlay

BGP Route Not Propagating? How to Check IRR Records and Fix IPv4 Routing Issues

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?

Why is my BGP session established but my prefix is not reachable?

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.

How do IRR records affect BGP filtering?

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.

What are the most common IRR mistakes?

Is the IPv4 route object missing?

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.

Does the IRR Origin ASN differ from the BGP announcement?

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.

Are old or conflicting route objects still present?

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.

Is the AS-SET incomplete?

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.

Is the provider using a different IRR source?

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.

How can I check an IRR route object and Origin ASN?

Start with your exact IPv4 prefix and the Origin ASN you intend to advertise:

  1. Look up the prefix in the relevant IRR database (for example, the RIPE Database).
  2. Find its route object and compare the origin field with the ASN visible in your BGP announcement.
  3. Check for duplicate or obsolete records in other IRR sources used by your provider.
  4. Confirm that the ASN appears in any AS-SET required by the provider's filtering policy.
  5. Compare IRR information with observed announcements in RIPEstat or a Looking Glass service.
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

How long do IRR changes take to affect routing?

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.

Why does an IPv4 prefix work in some networks but not others?

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.

How should I prepare leased IPv4 space for routing?

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.

How do I fix a route that is not propagating?

  1. Verify that your router advertises the exact prefix to the intended upstream.
  2. Ask the upstream whether it received and accepted the route. If it rejected the route, request the filter reason.
  3. Correct the route object, AS-SET membership or ROA identified by that check. Confirm when the upstream applied its refreshed policy.
  4. Check the origin and AS path from independent collectors, then test reachability from a previously affected network.

Is IRR the same as RPKI?

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.

What should I verify before going live?

  • BGP session is established and the intended prefix is being advertised.
  • Prefix and Origin ASN match the appropriate IRR route object.
  • No obsolete route objects or incomplete AS-SET membership interfere with filtering.
  • Your upstream trusts the relevant IRR source and has refreshed its filters.
  • ROA authorizations are consistent with the actual prefix and Origin ASN.
  • Independent collectors show the expected origin ASN, and reachability tests succeed from the networks you serve.
  • The holder, tenant and upstream know who owns routing changes and cleanup.

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.

Browse IPv4 Marketplace

Vladislava Shadrina

Customer Account Manager

    Articles
    Аренда/лизинг/покупка
    Аренда/лизинг/покупка

    Понимание различных типов и назначения IP-адресов

    More
    A Beginner’s Guide to Subnetting IPv4 and IPv6 Addresses (2026 Update)
    A Beginner’s Guide to Subnetting IPv4 and IPv6 Addresses (2026 Update)

    A Beginner’s Guide to Subnetting IPv4 and IPv6 Addresses Subnetting is a critical

    More
    IPv4 Leasing Revolution: Why Smart Businesses Are Ditching Ownership in 2025
    IPv4 Leasing Revolution: Why Smart Businesses Are Ditching Ownership in 2025

    Why IPv4 Leasing Is Becoming the Smart Choice for Businesses in 2025 1. Introduction

    More
    Network Isolation Revolution: IPv4 Marketplace Insights for Enterprise Security
    Network Isolation Revolution: IPv4 Marketplace Insights for Enterprise Security

      As CEO of InterLIR, I’ve witnessed firsthand how network isolation strategies

    More
    What is ASN?
    What is ASN?

    What is an ASN? ASN stands for Autonomous System Number. It is a unique identifier

    More
    How Anycast DNS Actually Works (And Why Your Network Needs It)
    How Anycast DNS Actually Works (And Why Your Network Needs It)

    Anycast DNS: A Leader’s Guide to Protecting Your Digital Infrastructure Executive

    More
    Why RPKI Matters: Securing Your Company’s Internet Traffic
    Why RPKI Matters: Securing Your Company’s Internet Traffic

    RPKI Certification: A Leader’s Guide to Internet Routing Security Executive

    More
    Why RIPE Address Policy Matters for Your Company’s Digital Future
    Why RIPE Address Policy Matters for Your Company’s Digital Future

    Executive Summary: What You Need to Know 🎯 Strategic Importance – Internet

    More
    AWS Outages: The CEO’s Guide to Preventing Downtime & Protecting Revenue
    AWS Outages: The CEO’s Guide to Preventing Downtime & Protecting Revenue

      When AWS DynamoDB failed in October 2025, thousands of businesses discovered that

    More
    What I Wish CEOs Knew About Managing IP Reputation Risk
    What I Wish CEOs Knew About Managing IP Reputation Risk

    Executive Summary: What You Need to Know 🎯 IP reputation directly impacts your

    More
    Cookie Consent with Real Cookie Banner Privacy settings