bgpreport

Network · data from 2026-11-12

AS7289 AS-QT - QuantaRa Tech LLC

Registry name: AS-QT - QuantaRa Tech LLC, US · not in PeeringDB

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

Announced routes

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

109.110.175.0/24 Invalid: origin Other origin only 2 0%low visibility 2
216.116.188.0/24 Valid None 671 100% 67
216.116.189.0/24 Valid None 670 100% 66
95.134.231.0/24 Valid Other IRR onlyRADB 671 100% 66
2a0c:5d40::/29 Valid RIR databaseRIPE 635 100% 67
2a11:240::/29 Valid RIR databaseRIPE 633 100% 67
2a11:a700::/29 Valid RIR databaseRIPE 633 100% 67
2a10:3e80::/29 Valid RIR databaseRIPE 632 99% 67
2a11:580::/29 Valid RIR databaseRIPE 632 99% 67
2a11:2000::/29 Valid RIR databaseRIPE 632 99% 67
2a11:4fc0::/29 Valid RIR databaseRIPE 632 99% 67
2a11:a400::/29 Valid RIR databaseRIPE 632 99% 67
2a11:d680::/29 Valid RIR databaseRIPE 632 99% 67
2a11:9f80::/29 Valid RIR databaseRIPE 630 99% 67
2a11:d780::/29 Valid RIR databaseRIPE 630 99% 67

AS-SET

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

  • ROA: origin1
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin109.110.175.0/24ROAs covering it name AS154073, not AS7289. If AS7289 should announce it, add a ROA for AS7289.2 of 673
Route object: none109.110.175.0/24Route objects for it name AS154073. Add a route object with origin AS7289 in the RIR database for the space.2 of 673
Route object: none216.116.188.0/24No route object for it. Add a route object with origin AS7289 in the RIR database for the space.671 of 673
Route object: none216.116.189.0/24No route object for it. Add a route object with origin AS7289 in the RIR database for the space.670 of 673
Route object: RIR95.134.231.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

2a05:64c0::/29RIPEValid
2a0e:ee80::/29RIPEValid
2a0f:3340::/29RIPEValid
2a11:1ac0::/29RIPEValid
2a12:7500::/29RIPEValid
2a12:e080::/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.