subnet.im

45.170.62.0/24

Massachusetts Institute of TechnologyAS3

MAXXTELECOM LTDAAS268142

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

60%

48 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 17th January 2019

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 45.170.62.0/24 as seen from Singapore, read outward from the origin: AS268142 → AS270738 → AS14840 → AS132337. Each hop is listed with its network name beneath the graph.AS268142MAXXTELECOM LTDAOriginAS270738Cedro TeleconAS14840BR.DIGITALAS132337Axclusive

Seen from Singapore

  1. 1AS268142MAXXTELECOM LTDABROrigin
    Peer of AS268142seen on 88 paths from 32 vantage points
  2. 2AS270738Cedro TeleconBR
    Peer of AS270738seen on 534 paths from 140 vantage points
  3. 3AS14840BR.DIGITAL BR
    Peer of AS14840seen on 5,396 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. Amsterdam26814227073814840213151This path
  2. Sao Paulo26814227073814840266213This path
  3. Singapore26814227073814840132337Shown above
  4. London, UK326814227368333568529This path
  5. Oregon, US3268142273683693920130This 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

60%

Seen by 48 of 80 full-feed vantage points

Partially propagated

Observed at 4 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
LACNIC — Latin America and the Caribbean
Country
Brazil
Allocated
17th January 2019
Allocation block
45.170.60.0/22
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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.170.62.0/24
PrefixAddressesOriginVisibility
45.170.63.0/24256AS268142MAXXTELECOM LTDA78/80

History

  1. AS26814212th August 2026 — present
  2. AS312th 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.170.62.0/24 in the calculator/24 reference

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