SUBNET.IM

45.64.79.0/24

At a glance

Addresses

256

/24 block

Visibility

60%

48 of 80 vantage points

RPKI

Valid

Registry

APNICTH

Allocated 13th June 2014

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Amsterdam.

OriginVantage point · Amsterdam
One AS path to 45.64.79.0/24 as seen from Amsterdam, read outward from the origin: AS38040 → AS6939 → AS58299 → AS41051 → AS213151. Each hop is listed with its network name beneath the graph.AS38040TOT Public Compan…OriginAS6939Hurricane Electri…AS58299Openfactory GmbH …AS41051Freetransit Proje…AS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS38040seen on 13,544 paths from 80 vantage points
  2. Peer of AS6939seen on 20,336 paths from 2 vantage points
  3. Peer of AS58299seen on 25,347 paths from 2 vantage points
  4. Peer of AS41051seen on 25,385 paths from 2 vantage points
  5. 5AS213151Christian ElsenDEVantage 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. Singapore38040132337This path
  2. London, UK380401374098529This path
  3. Sao Paulo38040262355266213This path
  4. Oregon, US38040693920130This path
  5. Amsterdam3804069395829941051213151Shown 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

60%

Seen by 48 of 80 full-feed vantage points

Partially 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
APNIC — Asia-Pacific
Country
Thailand
Allocated
13th June 2014
Allocation block
45.64.76.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.64.79.0/24
ROA prefixAuthorised originMax length
45.64.79.0/24AS38040/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.64.79.0/24
PrefixAddressesOriginVisibility
45.64.78.0/24256AS38040TOT Public Company Limited80/80

History

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

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