subnet.im

192.157.8.0/24

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

At a glance

Addresses

256

/24 block

Visibility

100%

78 of 78 vantage points

RPKI

Valid

Registry

RIPE NCCSE

Allocated 15th April 1992

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 192.157.8.0/24 as seen from Singapore, read outward from the origin: AS25252 → AS1257 → AS6939 → AS38623 → AS23673. Each hop is listed with its network name beneath the graph.AS25252Volvo Information…OriginAS1257Tele2 Sverige ABAS6939Hurricane Electri…AS38623Metfone (Viettel …AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS25252seen on 1,348 paths from 119 vantage points
  2. Peer of AS1257seen on 5,500 paths from 28 vantage points
  3. Peer of AS6939seen on 41,713 paths from 5 vantage points
  4. Peer of AS38623seen on 83,119 paths from 1 vantage 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. Amsterdam25252125782838298This path
  2. London, UK25252125764538529This path
  3. Sao Paulo252521257645335280This path
  4. Singapore25252125769393862323673Shown above
  5. Oregon, US252521257174855142013This 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

100%

Seen by 78 of 78 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
Sweden
Allocated
15th April 1992
Allocation block
192.157.8.0/21
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 192.157.8.0/24
ROA prefixAuthorised originMax length
192.157.8.0/24AS25252/24
192.157.8.0/24AS3301/24
192.157.8.0/23AS25252/23

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 192.157.8.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.192.157.8.0/23AS25252192.157.8.0/24AS25252This prefix192.157.9.0/24AS25252

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 192.157.8.0/24
PrefixAddressesOriginVisibility
192.157.8.0/23512AS25252Volvo Information Technology AB78/78

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 192.157.8.0/24
PrefixAddressesOriginVisibility
192.157.9.0/24256AS25252Volvo Information Technology AB78/78

History

  1. AS2525212th August 2026 — present
  2. AS330126th October 2026 — 26th 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 192.157.8.0/24 in the calculator/24 reference

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