subnet.im

157.22.70.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCSC

Allocated 14th October 1997

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 157.22.70.0/24 as seen from Singapore, read outward from the origin: AS44559 → AS209847 → AS49800 → AS12389 → AS4766 → AS132337. Each hop is listed with its network name beneath the graph.AS44559IT HOSTLINE LTDOriginAS209847WorkTitans B.V.AS49800GNC-Alfa CJSCAS12389Rostelecom PJSCAS4766Korea TelecomAS132337Axclusive

Seen from Singapore

  1. Peer of AS44559seen on 41,346 paths from 80 vantage points
  2. Peer of AS209847seen on 537 paths from 142 vantage points
  3. Peer of AS49800seen on 3,169 paths from 87 vantage points
  4. Peer of AS12389seen on 26,029 paths from 1 vantage point
  5. Peer of AS4766seen on 70,419 paths from 2 vantage points
  6. 6AS132337AxclusiveSGVantage 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. Amsterdam4455920984749800213151This path
  2. London, UK44559209847498008529This path
  3. Oregon, US4455920984749800693920130This path
  4. Sao Paulo445592098474980012993356266213This path
  5. Singapore4455920984749800123894766132337Shown above

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
RIPE NCC — Europe, Middle East, Central Asia
Country
Seychelles
Allocated
14th October 1997
Allocation block
157.22.0.0/17
Status
assigned
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 157.22.70.0/24
ROA prefixAuthorised originMax length
157.22.70.0/24AS44559/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 157.22.70.0/24
PrefixAddressesOriginVisibility
157.22.71.0/24256AS44559IT HOSTLINE LTD79/80

History

  1. AS4455912th 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 157.22.70.0/24 in the calculator/24 reference

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