bgpreport

Network · data from 2026-11-12

AS54702 QuickMeg

Registry name: QUICKMEG - QuickMeg Inc, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54702, 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.

143.14.92.0/24 Invalid: origin Other origin only 2 0%low visibility 2
102.129.234.0/24 Invalid: origin RIR databaseAFRINIC 2 0%low visibility 2
23.184.56.0/24 Valid RIR databaseARIN 673 100% 67
67.220.89.0/24 Valid RIR databaseARIN 673 100% 67
69.33.195.0/24 Valid RIR databaseARIN, RADB 673 100% 67
69.33.217.0/24 Valid RIR databaseARIN, RADB 673 100% 67
173.0.0.0/22 Valid RIR databaseARIN 673 100% 67
204.9.60.0/24 Valid RIR databaseARIN 673 100% 67
77.111.103.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
130.51.94.0/24 Valid RIR databaseARIN 672 100% 67
216.238.48.0/22 Valid RIR databaseARIN 671 100% 67

AS-SET

AS54702's PeeringDB record names no 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 16 are in fix.csv.

  • ROA: origin2
  • Route object: none1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: origin143.14.92.0/24ROAs covering it name AS214647, not AS54702. If AS54702 should announce it, add a ROA for AS54702.2 of 673
Route object: none143.14.92.0/24Route objects for it name AS214647. Add a route object with origin AS54702 in the RIR database for the space.2 of 673
ROA: origin102.129.234.0/24ROAs covering it name AS834, not AS54702. If AS54702 should announce it, add a ROA for AS54702.2 of 673

Route objects not announced

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

23.150.24.0/24ARINNo ROA
23.182.128.0/24ARINValid
64.112.82.0/23ARINNo ROA
103.99.86.0/24APNICValid
136.175.125.0/24ARINInvalid: origin
142.249.216.0/24ARINValid
208.65.176.0/22ARINNo ROA
208.72.208.0/24ARINValid
209.51.128.0/24ARINValid
209.51.134.0/24ARINValid
209.51.152.0/24ARINValid
2602:299::/36ARINNo ROA
2620:130:a000::/44ARINValid

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.