subnet.im

185.53.78.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCUA

Allocated 8th April 2014

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 185.53.78.0/24 as seen from Singapore, read outward from the origin: AS39608 → AS50263 → AS132337. Each hop is listed with its network name beneath the graph.AS39608Lanet Network LtdOriginAS50263A-Systems Sp. z o…AS132337Axclusive

Seen from Singapore

  1. Peer of AS39608seen on 419 paths from 17 vantage points
  2. Peer of AS50263seen on 8,475 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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. London, UK3960890028529This path
  2. Singapore3960850263132337Shown above
  3. Amsterdam39608352976939213151This path
  4. Sao Paulo39608352976939266213This path
  5. Oregon, US3960835297693920130This 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 80 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
Ukraine
Allocated
8th April 2014
Allocation block
185.53.78.0/24
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 185.53.78.0/24
ROA prefixAuthorised originMax length
185.53.78.0/24AS39608/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 185.53.78.0/24
PrefixAddressesOriginVisibility
185.53.79.0/24256AS16223MAXNET TELECOM, LTD80/80

History

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

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