subnet.im

213.193.240.0/24

IDC CubeAS401776

At a glance

Addresses

256

/24 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCNL

Allocated 28th June 2002

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 213.193.240.0/24 as seen from Singapore, read outward from the origin: AS401776 → AS62610 → AS29752 → AS21859 → AS132337. Each hop is listed with its network name beneath the graph.AS401776IDC CubeOriginAS62610Zenlayer IncAS29752Zenlayer IncAS21859Zenlayer IncAS132337Axclusive

Seen from Singapore

  1. 1AS401776IDC CubeUSOrigin
    Peer of AS401776seen on 2,316 paths from 143 vantage points
  2. 2AS62610Zenlayer IncUS
    Peer of AS62610seen on 31,588 paths from 145 vantage points
  3. 3AS29752Zenlayer IncUS
    Peer of AS29752seen on 6,338 paths from 95 vantage points
  4. 4AS21859Zenlayer IncUS
    Peer of AS21859seen on 9,315 paths from 2 vantage points
  5. 5AS132337AxclusiveSGVantage point

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. Amsterdam4017766261029752218598298This path
  2. London, UK40177662610297522185935280This path
  3. Singapore401776626102975221859132337Shown above
  4. Sao Paulo4017766261029752174645335280This path
  5. Oregon, US40177662610297524229693920130This 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 80 of 81 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
28th June 2002
Allocation block
213.193.240.0/22
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 213.193.240.0/24
ROA prefixAuthorised originMax length
213.193.240.0/24AS401776/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 213.193.240.0/24
PrefixAddressesOriginVisibility
213.193.241.0/24256AS214647Yadda OU81/81

History

  1. AS40177622nd September 2026 — present
  2. AS20548912th August 2026 — 21st September 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 213.193.240.0/24 in the calculator/24 reference

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