bgpreport

Network · data from 2026-11-12

AS2494 MUWNET - IDDQD-AS

Registry name: MUWNET - IDDQD-AS, AT · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 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
5Route objects not announced registered with origin AS2494, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS2494, 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.
149.148.0.0/16 No ROA RIR databaseRIPE 671 100% 69
2001:67c:27c::/48 No ROA RIR databaseRIPE 636 100% 70

AS-SET

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

  • ROA: none2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none149.148.0.0/16No ROA covers it. Add a ROA for AS2494, maxLength 16.671 of 673
ROA: none2001:67c:27c::/48No ROA covers it. Add a ROA for AS2494, maxLength 48.636 of 636

Route objects not announced

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

193.170.111.0/24RIPEInvalid: origin
193.171.159.0/24RIPEInvalid: origin
193.171.160.0/20RIPEInvalid: origin
193.171.176.0/21RIPEInvalid: origin
193.171.184.0/22RIPEInvalid: origin

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.