SUBNET.IM

130.78.48.0/22

Dimensione S.r.l.AS202870

At a glance

Addresses

1,024

/22 block

Visibility

19%

15 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCIT

Allocated 24th June 1988

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: 4 observed paths to 130.78.48.0/22, fanning out from AS202870 toward the vantage points that see it. Each path is written out in full beneath the graph.AS202870Dimensione S.r.l.OriginAS132337AxclusiveAS137409GSL Networks Pty …AS8529Zain Omantel Inte…AS262355VSX NetworksAS266213PLANETCLICK TELEC…AS13030Init7 (Switzerlan…AS58299Openfactory GmbH …AS41051Freetransit Proje…AS213151Christian Elsen
  1. Singapore202870132337This path
  2. London, UK2028701374098529This path
  3. Sao Paulo202870262355266213This path
  4. Amsterdam202870130305829941051213151This 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

19%

Seen by 15 of 80 full-feed vantage points

Seen by few vantage points

Observed at 4 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
Italy
Allocated
24th June 1988
Allocation block
130.78.32.0/19
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 130.78.48.0/22
ROA prefixAuthorised originMax length
130.78.32.0/19AS202870/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 130.78.48.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.130.78.48.0/21AS202870130.78.48.0/22AS202870This prefix130.78.52.0/22AS202870

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 130.78.48.0/22
PrefixAddressesOriginVisibility
130.78.48.0/212kAS202870Dimensione S.r.l.80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 130.78.48.0/22
PrefixAddressesOriginVisibility
130.78.52.0/221kAS202870Dimensione S.r.l.15/80

History

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

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