bgpreport

Network · data from 2026-11-12

AS207996 ungleich-place6 ungleich glarus ag

Registry name: ungleich-place6 ungleich glarus ag, CH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207996, 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.

2a0a:e5c0:19::/48 Valid Other origin only 635 100% 69
2a0a:e5c1:100::/40 Valid RIR databaseRIPE 636 100% 69
2a0a:e5c1:700::/40 Valid RIR databaseRIPE 636 100% 69
2a0a:e5c0:12::/48 Valid RIR databaseRIPE 635 100% 69
2a0a:e5c0:26::/48 Valid RIR databaseRIPE 635 100% 69
2a0a:e5c0:27::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS207996 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 36 are in fix.csv.

  • Route object: none1
  • Route object: not announced35
ChangePrefix or setDetailFull-table peers
Route object: none2a0a:e5c0:19::/48Route objects for it name AS213081. Add a route object with origin AS207996 in the RIR database for the space.635 of 636

Route objects not announced

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

147.78.194.0/24RIPEValid
147.78.195.0/24RIPEValid
185.155.29.0/24RIPEValid
185.203.114.0/23RIPEInvalid: origin
2a09:2940::/29RIPEValid
2a0a:e5c0:2::/48RIPEValid
2a0a:e5c0:3::/48RIPEValid
2a0a:e5c0:7::/48RIPEValid
2a0a:e5c0:8::/48RIPEValid
2a0a:e5c0:e::/48RIPEValid
2a0a:e5c0:f::/48RIPEValid
2a0a:e5c0:10::/48RIPEValid
2a0a:e5c0:13::/48RIPEValid
2a0a:e5c0:16::/48RIPEValid
2a0a:e5c0:17::/48RIPEValid
2a0a:e5c0:1b::/48RIPEValid
2a0a:e5c0:1c::/48RIPEValid
2a0a:e5c0:1d::/48RIPEValid
2a0a:e5c0:1e::/48RIPEValid
2a0a:e5c0:28::/48RIPEValid
2a0a:e5c0:29::/48RIPEValid
2a0a:e5c0:2c::/48RIPEValid
2a0a:e5c0:42::/48RIPEValid
2a0a:e5c0:43::/48RIPEValid
2a0a:e5c0:44::/48RIPEValid
2a0a:e5c0:60::/48RIPEValid
2a0a:e5c0:61::/48RIPEValid
2a0a:e5c0:62::/48RIPEValid
2a0a:e5c0:63::/48RIPEValid
2a0a:e5c1::/32RIPEValid
2a0a:e5c1:200::/40RIPEValid
2a0a:e5c1:300::/40RIPEValid
2a0a:e5c1:600::/40RIPEValid
2a0a:e5c1:c00::/40RIPEValid
2a0a:e5c4::/32RIPEValid

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.