subnet.im

170.83.100.0/22

FAXT Telecomunicações Ltda.AS52601

At a glance

Addresses

1,024

/22 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 5th January 2017

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 170.83.100.0/22 as seen from Amsterdam, read outward from the origin: AS52601 → AS263652 → AS269096 → AS7195 → AS213151. Each hop is listed with its network name beneath the graph.AS52601FAXT Telecomunica…OriginAS263652BIZZ INTERNET LTDAAS269096NORTH TECNOLOGIAAS7195EdgeUnoAS213151Christian Elsen

Seen from Amsterdam

  1. 1AS52601FAXT Telecomunicações Ltda.BROrigin
    Peer of AS52601seen on 80 paths from 80 vantage points
  2. 2AS263652BIZZ INTERNET LTDABR
    Peer of AS263652seen on 700 paths from 142 vantage points
  3. 3AS269096NORTH TECNOLOGIABR
    Peer of AS269096seen on 18,077 paths from 124 vantage points
  4. 4AS7195EdgeUnoCO
    Peer of AS7195seen on 13,739 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. Sao Paulo52601263652269096266213This path
  2. Amsterdam526012636522690967195213151Shown above
  3. London, UK5260126365226909633568529This path
  4. Singapore526012636522690967195132337This path
  5. Oregon, US526012636522690963356693920130This 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
LACNIC — Latin America and the Caribbean
Country
Brazil
Allocated
5th January 2017
Allocation block
170.83.100.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 170.83.100.0/22
ROA prefixAuthorised originMax length
170.83.100.0/22AS52601/32

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 170.83.100.0/22
PrefixAddressesOriginVisibility
170.83.96.0/221kAS61588DIGITAL PROVEDOR DE ACESSO A INTERNET LTDA80/80

History

  1. AS5260112th 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 170.83.100.0/22 in the calculator/22 reference

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