bgpreport

Network · data from 2026-11-12

AS219208 QMQ-AS MAOQUN QIU

Registry name: QMQ-AS MAOQUN QIU, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS219208, 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.
2a0b:a304::/30 Invalid: origin None 3 0%low visibility 3
2a0b:a300::/30 Invalid: origin None 1 0%low visibility 1
2a14:7582:7000::/37 Invalid: origin None 1 0%low visibility 1
2a0f:a704::/30 No ROA None 3 0%low visibility 3
2a0f:a700::/30 No ROA None 1 0%low visibility 1
2a06:9801:1300::/40 Valid RIR databaseRIPE 636 100% 67
2a0d:2681:8000::/33 Valid RIR databaseRIPE 636 100% 67
2a0d:d941::/37 Valid RIR databaseRIPE 636 100% 67
2a10:fa86::/34 Valid RIR databaseRIPE 634 100% 67
2a0a:d682:d000::/36 Valid RIR databaseRIPE 632 99% 67
2a14:5f00::/30 Valid RIR databaseRIPE 632 99% 67
2a0f:6280:7400::/39 Valid RIR databaseRIPE 631 99% 67

AS-SET

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

  • ROA: origin3
  • ROA: none2
  • Route object: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin2a0b:a304::/30ROAs covering it name AS55286, not AS219208. If AS219208 should announce it, add a ROA for AS219208.3 of 636
Route object: none2a0b:a304::/30No route object for it. Add a route object with origin AS219208 in the RIR database for the space.3 of 636
ROA: origin2a0b:a300::/30ROAs covering it name AS55286, not AS219208. If AS219208 should announce it, add a ROA for AS219208.1 of 636
Route object: none2a0b:a300::/30No route object for it. Add a route object with origin AS219208 in the RIR database for the space.1 of 636
ROA: origin2a14:7582:7000::/37An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS219208 should announce it, add a ROA for AS219208.1 of 636
Route object: none2a14:7582:7000::/37No route object for it. Add a route object with origin AS219208 in the RIR database for the space.1 of 636
ROA: none2a0f:a704::/30No ROA covers it. Add a ROA for AS219208, maxLength 30.3 of 636
Route object: none2a0f:a704::/30No route object for it. Add a route object with origin AS219208 in the RIR database for the space.3 of 636
ROA: none2a0f:a700::/30No ROA covers it. Add a ROA for AS219208, maxLength 30.1 of 636
Route object: none2a0f:a700::/30No route object for it. Add a route object with origin AS219208 in the RIR database for the space.1 of 636

Route objects not announced

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

2a0a:d687:ff03::/48RIPEValid
2a14:5f00::/29RIPEValid

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.