SUBNET.IM

5.102.68.0/22

At a glance

Addresses

1,024

/22 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCPL

Allocated 27th June 2012

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.102.68.0/22, fanning out from AS41023 toward the vantage points that see it. Each path is written out in full beneath the graph.AS41023AGENCJA ROZWOJU R…OriginAS29535Orange Polska Spo…AS8529Zain Omantel Inte…AS6939Hurricane Electri…AS213151Christian ElsenAS266213PLANETCLICK TELEC…AS20804Exatel S.A.AS50263A-Systems Sp. z o…AS132337AxclusiveAS20130Depaul University
  1. London, UK41023295358529This path
  2. Amsterdam41023295356939213151This path
  3. Sao Paulo41023295356939266213This path
  4. Singapore410232080450263132337This path
  5. Oregon, US4102329535693920130This 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
Poland
Allocated
27th June 2012
Allocation block
5.102.64.0/21
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.102.68.0/22
ROA prefixAuthorised originMax length
5.102.68.0/22AS41023/22

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 5.102.68.0/22: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.5.102.68.0/22AS41023This prefix5.102.71.0/24AS41023

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 5.102.68.0/22
PrefixAddressesOriginVisibility
5.102.71.0/24256AS41023AGENCJA ROZWOJU REGIONALNEGO "ARREKS" Sp z.o.o80/80

Sibling prefixes

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

History

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

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