subnet.im

168.227.124.0/23

At a glance

Addresses

512

/23 block

Visibility

100%

82 of 82 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 18th March 2016

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 168.227.124.0/23 as seen from Amsterdam, read outward from the origin: AS264879 → AS263400 → AS271253 → AS8298. Each hop is listed with its network name beneath the graph.AS264879Nova Internet e T…OriginAS263400NEONET SERVIÇO CO…AS271253LINK BRASIL TELEC…AS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS264879seen on 258 paths from 129 vantage points
  2. Peer of AS263400seen on 3,418 paths from 147 vantage points
  3. Peer of AS271253seen on 1,254 paths from 1 vantage point
  4. 4AS8298IPng Networks GmbHCHVantage 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. Amsterdam2648792634002712538298Shown above
  2. Sao Paulo26487926340027125335280This path
  3. Singapore2648792634001031132337This path
  4. London, UK264879263400271253335635280This path
  5. Oregon, US264879263400271253693920130This 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 82 of 82 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
18th March 2016
Allocation block
168.227.124.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 168.227.124.0/23
ROA prefixAuthorised originMax length
168.227.124.0/23AS264879/23
168.227.124.0/22AS264879/22

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 168.227.124.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.168.227.124.0/22AS264879168.227.124.0/23AS264879This prefix168.227.126.0/23AS264879

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 168.227.124.0/23
PrefixAddressesOriginVisibility
168.227.124.0/221kAS264879Nova Internet e Tecnologia Ltda Me82/82

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 168.227.124.0/23
PrefixAddressesOriginVisibility
168.227.126.0/23512AS264879Nova Internet e Tecnologia Ltda Me82/82

History

  1. AS26487922nd September 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 168.227.124.0/23 in the calculator/23 reference

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