subnet.im

159.253.5.0/24

AS14293 is not currently observed originating this prefix. The origins we do see are listed above.

At a glance

Addresses

256

/24 block

Visibility

99%

75 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCNL

Allocated 20th September 2011

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 159.253.5.0/24 as seen from Singapore, read outward from the origin: AS136809 → AS62610 → AS29752 → AS4229 → AS57463 → AS23673. Each hop is listed with its network name beneath the graph.AS136809FAST ZONE ITOriginAS62610Zenlayer IncAS29752Zenlayer IncAS4229Zenlayer IncAS57463NetIX Communicati…AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS136809seen on 3,602 paths from 75 vantage points
  2. Peer of AS62610seen on 41,308 paths from 138 vantage points
  3. Peer of AS29752seen on 16,375 paths from 121 vantage points
  4. Peer of AS4229seen on 4,573 paths from 55 vantage points
  5. Peer of AS57463seen on 1,616 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. Amsterdam136809626102975242298298This path
  2. London, UK136809626102975242298529This path
  3. Sao Paulo1368096261029752174645335280This path
  4. Singapore136809626102975242295746323673Shown above
  5. Oregon, US136809626102975232572335220130This 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 75 of 76 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Netherlands
Allocated
20th September 2011
Allocation block
159.253.0.0/21
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 159.253.5.0/24
ROA prefixAuthorised originMax length
159.253.5.0/24AS136809/24
159.253.5.0/24AS14293/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

Prefixes of the same length sharing a parent block with 159.253.5.0/24
PrefixAddressesOriginVisibility
159.253.4.0/24256AS214143SKYDIGITAL TELECOM LTD76/76

History

  1. AS13680922nd October 2026 — present
  2. AS1429322nd October 2026 — 22nd October 2026
  3. AS5335612th August 2026 — 6th October 2026
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 159.253.5.0/24 in the calculator/24 reference

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