bgpreport

Network · data from 2026-11-12

AS212799 NET1 Net1 GmbH

Registry name: NET1 Net1 GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS212799, 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.
2a07:87c0:fe00::/48 No ROA RIR databaseRIPE 605 95% 67
2a07:87c0:ffff::/48 No ROA RIR databaseRIPE 605 95% 67

AS-SET

AS212799 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: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a07:87c0:fe00::/48No ROA covers it. Add a ROA for AS212799, maxLength 48.605 of 636
ROA: none2a07:87c0:ffff::/48No ROA covers it. Add a ROA for AS212799, maxLength 48.605 of 636

Route objects not announced

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

2602:fd50:f10::/48ARINNo ROA
2602:fd50:f40::/44ARINNo 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.