SUBNET.IM

223.234.0.0/16

At a glance

Addresses

65,536

/16 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

APNICIN

Allocated 14th September 2010

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to London, UK.

OriginVantage point · London, UK
One AS path to 223.234.0.0/16 as seen from London, UK, read outward from the origin: AS45609 → AS9498 → AS1299 → AS8529. Each hop is listed with its network name beneath the graph.AS45609Bharti Airtel Ltd…OriginAS9498Bharti Airtel Ltd.AS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS45609seen on 382,642 paths from 141 vantage points
  2. Peer of AS9498seen on 150,510 paths from 108 vantage points
  3. Peer of AS1299seen on 403,291 paths from 2 vantage points

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Singapore456099498132337This path
  2. London, UK45609949812998529Shown above
  3. Oregon, US456099498693920130This path
  4. Amsterdam456099498646134549213151This path
  5. Sao Paulo45609949834913356266213This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

99%

Seen by 79 of 80 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
APNIC — Asia-Pacific
Country
India
Allocated
14th September 2010
Allocation block
223.232.0.0/13
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 223.234.0.0/16
ROA prefixAuthorised originMax length
223.232.0.0/13AS45609/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS4560912th August 2026 present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 223.234.0.0/16 in the calculator/16 reference

Routing data derived from RouteViews MRT archives and public registry data.