bgpreport

Network · data from 2026-11-12

AS57667 UPTIME-IT-01 Uptime IT GmbH

Registry name: UPTIME-IT-01 Uptime IT GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57667, 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.
185.96.12.0/24 No ROA RIR databaseRIPE 673 100% 67
185.96.14.0/24 No ROA RIR databaseRIPE 673 100% 67
195.137.225.0/24 No ROA RIR databaseRIPE 673 100% 67
45.85.40.0/24 No ROA RIR databaseRIPE 672 100% 67
45.85.41.0/24 No ROA RIR databaseRIPE 672 100% 67
45.85.42.0/24 No ROA RIR databaseRIPE 672 100% 67
46.30.0.0/24 No ROA RIR databaseRIPE 672 100% 67
46.30.2.0/24 No ROA RIR databaseRIPE 672 100% 67
46.30.3.0/24 No ROA RIR databaseRIPE 672 100% 67
46.30.5.0/24 No ROA RIR databaseRIPE 672 100% 67
46.30.6.0/24 No ROA RIR databaseRIPE 672 100% 67
46.30.7.0/24 No ROA RIR databaseRIPE 672 100% 67
185.96.13.0/24 No ROA RIR databaseRIPE 671 100% 67
185.96.15.0/24 No ROA RIR databaseRIPE 671 100% 67
46.30.1.0/24 No ROA RIR databaseRIPE 670 100% 67
46.30.4.0/24 No ROA RIR databaseRIPE 670 100% 67

AS-SET

AS57667 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 24 are in fix.csv.

  • ROA: none16
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none185.96.12.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.673 of 673
ROA: none185.96.14.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.673 of 673
ROA: none195.137.225.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.673 of 673
ROA: none45.85.40.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.672 of 673
ROA: none45.85.41.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.672 of 673
ROA: none45.85.42.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.672 of 673
ROA: none46.30.0.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.672 of 673
ROA: none46.30.2.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.672 of 673
ROA: none46.30.3.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.672 of 673
ROA: none46.30.5.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.672 of 673
ROA: none46.30.6.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.672 of 673
ROA: none46.30.7.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.672 of 673
ROA: none185.96.13.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.671 of 673
ROA: none185.96.15.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.671 of 673
ROA: none46.30.1.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.670 of 673
ROA: none46.30.4.0/24No ROA covers it. Add a ROA for AS57667, maxLength 24.670 of 673

Route objects not announced

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

46.30.0.0/23RIPENo ROA
185.238.24.0/24RIPENo ROA
2a05:f780:1000::/36RIPENo ROA
2a05:f780:2000::/36RIPENo ROA
2a05:f780:3000::/36RIPENo ROA
2a05:f780:4000::/36RIPENo ROA
2a05:f780:5000::/36RIPENo ROA
2a05:f787:ffff::/48RIPENo ROA

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.