subnet.im

131.0.78.0/23

GGNET TELECOMUNICACOES LTDAAS53062

At a glance

Addresses

512

/23 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 7th July 2014

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 131.0.78.0/23 as seen from London, UK, read outward from the origin: AS53062 → AS174 → AS6453 → AS8529. Each hop is listed with its network name beneath the graph.AS53062GGNET TELECOMUNIC…OriginAS174Cogent Communicat…AS6453TATA Communicatio…AS8529Zain Omantel Inte…

Seen from London, UK

  1. 1AS53062GGNET TELECOMUNICACOES LTDABROrigin
    Peer of AS53062seen on 3,542 paths from 102 vantage points
  2. 2AS174Cogent Communications, LLCUS
    Peer of AS174seen on 531,328 paths from 53 vantage points
  3. 3AS6453TATA Communications (America) IncUS
    Peer of AS6453seen on 89,408 paths from 35 vantage points
  4. 4AS8529Zain Omantel International FZ-LLCAEVantage 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 Paulo53062266213This path
  2. Singapore5306252468132337This path
  3. London, UK5306217464538529Shown above
  4. Amsterdam53062524683746834549213151This path
  5. Oregon, US5306252468374681299693920130This 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
7th July 2014
Allocation block
131.0.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 131.0.78.0/23
ROA prefixAuthorised originMax length
131.0.76.0/22AS53062/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 131.0.78.0/23
PrefixAddressesOriginVisibility
131.0.76.0/23512AS53062GGNET TELECOMUNICACOES LTDA80/80

History

  1. AS5306212th 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 131.0.78.0/23 in the calculator/23 reference

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