bgpreport

Network · data from 2026-11-12

AS47777 wunet Mightycare Solutions GmbH

Registry name: wunet Mightycare Solutions GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47777, 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.
2a00:1b40:2::/48 Valid Nonecovered by 2a00:1b40::/32 627 99% 67
2a00:1b40:3::/48 Valid Nonecovered by 2a00:1b40::/32 627 99% 67
46.19.56.0/21 Valid RIR databaseRIPE 673 100% 67
94.125.24.0/21 Valid RIR databaseRIPE 673 100% 67
185.15.180.0/22 Valid RIR databaseRIPE 673 100% 67
2a00:1b40::/32 Valid RIR databaseRIPE 627 99% 67

AS-SET

AS47777 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.

  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2a00:1b40:2::/48No route object for it. A route object for 2a00:1b40::/32 with origin AS47777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47777 in the RIR database for the space.627 of 636
Route object: none2a00:1b40:3::/48No route object for it. A route object for 2a00:1b40::/32 with origin AS47777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47777 in the RIR database for the space.627 of 636

Route objects not announced

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

94.125.28.0/24RIPEValid
185.15.183.0/24RIPEValid

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.