SUBNET.IM

177.69.0.0/16

At a glance

Addresses

65,536

/16 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 21st June 2011

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 177.69.0.0/16 as seen from London, UK, read outward from the origin: AS16735 → AS6762 → AS8529. Each hop is listed with its network name beneath the graph.AS16735Algar TelecomOriginAS6762Telecom Italia Sp…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS16735seen on 42,275 paths from 137 vantage points
  2. Peer of AS6762seen on 33,111 paths from 1 vantage 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 Paulo16735266213This path
  2. London, UK1673567628529Shown above
  3. Singapore167356939132337This path
  4. Oregon, US16735693920130This path
  5. Amsterdam1673517434549213151This 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

99%

Seen by 79 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
21st June 2011
Allocation block
177.69.0.0/16
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 177.69.0.0/16
PrefixAddressesOriginVisibility
177.68.0.0/1665.5kAS27699Vivo (TELEFÔNICA BRASIL)79/80

History

  1. AS1673512th 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 177.69.0.0/16 in the calculator/16 reference

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