bgpreport

Network · data from 2026-11-12

AS44415 NETPARTNER-WWA1 GlobTel GmbH

Registry name: NETPARTNER-WWA1 GlobTel GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44415, 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.
194.54.85.0/24 Invalid: maxLength RIR databaseRIPE 13 2%low visibility 8
194.54.86.0/24 Invalid: maxLength RIR databaseRIPE 13 2%low visibility 8
194.54.87.0/24 Invalid: maxLength RIR databaseRIPE 13 2%low visibility 8
194.8.66.0/23 Valid RIR databaseRIPE 672 100% 66
194.54.84.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS44415 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 4 are in fix.csv.

  • ROA: maxLength3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength194.54.85.0/24ROA 194.54.84.0/22 AS44415 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 194.54.85.0/24.13 of 673
ROA: maxLength194.54.86.0/24ROA 194.54.84.0/22 AS44415 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 194.54.86.0/24.13 of 673
ROA: maxLength194.54.87.0/24ROA 194.54.84.0/22 AS44415 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 194.54.87.0/24.13 of 673

Route objects not announced

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

193.219.113.0/24RIPENo 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.