bgpreport

Network · data from 2026-11-12

AS199163 UBL Informationssysteme

Registry name: UBL-IS-ASN DATAGROUP Operations GmbH, DE · PeeringDB

8IPv4 routes 12.5% RPKI valid · 87.5% with a route object
5IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
12No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS199163, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS199163, 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.
81.91.23.0/24 No ROA Nonecovered by 81.91.16.0/21 672 100% 67
81.91.16.0/21 No ROA RIR databaseRIPE 673 100% 67
185.133.8.0/22 No ROA RIR databaseRIPE 673 100% 67
185.161.156.0/22 No ROA RIR databaseRIPE 673 100% 67
185.163.36.0/22 No ROA RIR databaseRIPE 673 100% 67
185.169.124.0/22 No ROA RIR databaseRIPE 673 100% 67
81.91.16.0/24 No ROA RIR databaseRIPE 669 99% 67
2a01:ae40::/32 No ROA RIR databaseRIPE 627 99% 67
2a05:cf40::/29 No ROA RIR databaseRIPE 626 98% 67
2a07:c600::/29 No ROA RIR databaseRIPE 626 98% 67
2a0a:4500::/29 No ROA RIR databaseRIPE 626 98% 67
2a0a:9800::/29 No ROA RIR databaseRIPE 626 98% 67
185.121.68.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS199163's PeeringDB record names no 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 13 are in fix.csv.

  • ROA: none12
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none81.91.23.0/24No ROA covers it. Add a ROA for AS199163, maxLength 24.672 of 673
Route object: none81.91.23.0/24No route object for it. A route object for 81.91.16.0/21 with origin AS199163 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199163 in the RIR database for the space.672 of 673
ROA: none81.91.16.0/21No ROA covers it. Add a ROA for AS199163, maxLength 21.673 of 673
ROA: none185.133.8.0/22No ROA covers it. Add a ROA for AS199163, maxLength 22.673 of 673
ROA: none185.161.156.0/22No ROA covers it. Add a ROA for AS199163, maxLength 22.673 of 673
ROA: none185.163.36.0/22No ROA covers it. Add a ROA for AS199163, maxLength 22.673 of 673
ROA: none185.169.124.0/22No ROA covers it. Add a ROA for AS199163, maxLength 22.673 of 673
ROA: none81.91.16.0/24No ROA covers it. Add a ROA for AS199163, maxLength 24.669 of 673
ROA: none2a01:ae40::/32No ROA covers it. Add a ROA for AS199163, maxLength 32.627 of 636
ROA: none2a05:cf40::/29No ROA covers it. Add a ROA for AS199163, maxLength 29.626 of 636
ROA: none2a07:c600::/29No ROA covers it. Add a ROA for AS199163, maxLength 29.626 of 636
ROA: none2a0a:4500::/29No ROA covers it. Add a ROA for AS199163, maxLength 29.626 of 636
ROA: none2a0a:9800::/29No ROA covers it. Add a ROA for AS199163, maxLength 29.626 of 636

Route objects not announced

Every route object with origin AS199163 is announced.

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.