SUBNET.IM

5.183.72.0/22

At a glance

Addresses

1,024

/22 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 10th April 2019

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 5.183.72.0/22, fanning out from AS35258 toward the vantage points that see it. Each path is written out in full beneath the graph.AS35258akquinet outsourc…OriginAS8529Zain Omantel Inte…AS9211Nawork Internet I…AS6939Hurricane Electri…AS213151Christian ElsenAS266213PLANETCLICK TELEC…AS20130Depaul UniversityAS50629LWLcom GmbHAS50263A-Systems Sp. z o…AS132337Axclusive
  1. London, UK352588529This path
  2. Amsterdam3525892116939213151This path
  3. Sao Paulo3525892116939266213This path
  4. Oregon, US352589211693920130This path
  5. Singapore3525892115062950263132337This 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Germany
Allocated
10th April 2019
Allocation block
5.183.72.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 5.183.72.0/22
ROA prefixAuthorised originMax length
5.183.72.0/22AS35258/22

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

No prefix of the same length in the same parent block is announced.

History

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

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