subnet.im

178.157.77.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

78 of 78 vantage points

RPKI

Valid

Registry

RIPE NCCRO

Allocated 28th June 2010

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 178.157.77.0/24 as seen from Singapore, read outward from the origin: AS58126 → AS5541 → AS12310 → AS6939 → AS23673. Each hop is listed with its network name beneath the graph.AS58126VINCI COMMUNICATI…OriginAS5541INVITE Systems SRLAS12310iNES GROUP SRLAS6939Hurricane Electri…AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS58126seen on 196 paths from 49 vantage points
  2. Peer of AS5541seen on 539 paths from 142 vantage points
  3. Peer of AS12310seen on 10,156 paths from 107 vantage points
  4. Peer of AS6939seen on 358,340 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. London, UK5812690098529This path
  2. Amsterdam5812655411231069398298This path
  3. Sao Paulo58126554112310693935280This path
  4. Singapore58126554112310693923673Shown above
  5. Oregon, US581265541123109002855142013This 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
Romania
Allocated
28th June 2010
Allocation block
178.157.64.0/20
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 178.157.77.0/24
ROA prefixAuthorised originMax length
178.157.77.0/24AS58126/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 178.157.77.0/24
PrefixAddressesOriginVisibility
178.157.76.0/24256AS9009M247 Europe SRL78/78

History

  1. AS5812622nd September 2026 — present
  2. AS19942912th 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 178.157.77.0/24 in the calculator/24 reference

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