subnet.im

45.155.242.0/24

Tan Kok FengAS204535

FAST ZONE ITAS136809

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

99%

75 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCES

Allocated 19th September 2019

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 45.155.242.0/24 as seen from London, UK, read outward from the origin: AS204535 → AS206216 → AS137409 → AS6939 → AS8529. Each hop is listed with its network name beneath the graph.AS204535Tan Kok FengOriginAS206216Advin Services LLCAS137409GSL Networks Pty …AS6939Hurricane Electri…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS204535seen on 846 paths from 138 vantage points
  2. Peer of AS206216seen on 1,598 paths from 138 vantage points
  3. Peer of AS137409seen on 9,072 paths from 22 vantage points
  4. Peer of AS6939seen on 262,276 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. Amsterdam2045352062161374098298This path
  2. Sao Paulo20453520621613740935280This path
  3. Singapore20453520621613740923673This path
  4. London, UK20453520621613740969398529Shown above
  5. Oregon, US204535206216137409693920130This 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
Spain
Allocated
19th September 2019
Allocation block
45.155.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 45.155.242.0/24
ROA prefixAuthorised originMax length
45.155.242.0/24AS136809/24
45.155.242.0/24AS204535/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 45.155.242.0/24
PrefixAddressesOriginVisibility
45.155.243.0/24256AS211373Simoresta UAB76/76

History

  1. AS13680922nd October 2026 — present
  2. AS20453522nd October 2026 — present
  3. AS551112th August 2026 — 12th 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 45.155.242.0/24 in the calculator/24 reference

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