SUBNET.IM

45.83.144.0/22

At a glance

Addresses

1,024

/22 block

Visibility

9%

7 of 80 vantage points

RPKI

Invalid

Registry

RIPE NCCCZ

Allocated 27th May 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: 2 observed paths to 45.83.144.0/22, fanning out from AS34549 toward the vantage points that see it. Each path is written out in full beneath the graph.AS34549meerfarbig GmbH &…OriginAS213151Christian ElsenAS8966Etisalat (E&)AS132337Axclusive
  1. Amsterdam34549213151This path
  2. Singapore345498966132337This 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

9%

Seen by 7 of 80 full-feed vantage points

Seen by few vantage points

Observed at 3 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
Czechia
Allocated
27th May 2019
Allocation block
45.83.144.0/22
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 45.83.144.0/22
ROA prefixAuthorised originMax length
45.83.144.0/22AS212238/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 45.83.144.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.45.83.144.0/22AS34549This prefix45.83.144.0/24AS21223845.83.145.0/24AS21223845.83.146.0/24AS21223845.83.147.0/24AS212238

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 45.83.144.0/22
PrefixAddressesOriginVisibility
45.83.144.0/24256AS212238Datacamp Limited79/80
45.83.145.0/24256AS212238Datacamp Limited80/80
45.83.146.0/24256AS212238Datacamp Limited80/80
45.83.147.0/24256AS212238Datacamp Limited79/80

Sibling prefixes

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

History

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

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