bgpreport

Network · data from 2026-11-12

AS43844 UPPSALA-STUDENT-NETWORK Uppsala Student Network

Registry name: UPPSALA-STUDENT-NETWORK Uppsala Student Network, SE · not in PeeringDB

5IPv4 routes 60.0% RPKI valid · 80.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS43844, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS43844, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

130.242.96.0/20 No ROA RIR databaseRIPE 672 100% 68
130.243.128.0/17 No ROA RIR databaseRIPE 672 100% 68
212.25.130.0/23 Valid None 672 100% 68
212.25.144.0/21 Valid RIR databaseRIPE 672 100% 68
212.25.152.0/22 Valid RIR databaseRIPE 672 100% 68

AS-SET

AS43844 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 5 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none130.242.96.0/20No ROA covers it. Add a ROA for AS43844, maxLength 20.672 of 673
ROA: none130.243.128.0/17No ROA covers it. Add a ROA for AS43844, maxLength 17.672 of 673
Route object: none212.25.130.0/23No route object for it. Add a route object with origin AS43844 in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS43844 whose prefix no peer sees AS43844 announce. Many are kept on purpose (backup routes, space announced only in some places).

212.25.130.0/24RIPEValid
212.25.131.0/24RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.