Network · data from 2026-11-12
AS198499 Qatar University
Registry name: QUNIV Qatar University, QA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198499, 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.
| 86.36.64.0/19 | Valid | None | 673 100% |
| 2a00:f0e0::/32 | Valid | None | 633 100% |
| 185.37.111.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 86.36.64.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 86.36.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 185.37.108.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.37.110.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 2a00:f0e0:10::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a00:f0e0:40::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a00:f0e0:70::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS198499'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 25 are in fix.csv.
- Route object: none2
- Route object: RIR1
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 86.36.64.0/19 | No route object for it. Add a route object with origin AS198499 in the RIR database for the space. |
| Route object: none | 2a00:f0e0::/32 | No route object for it. Add a route object with origin AS198499 in the RIR database for the space. |
| Route object: RIR | 185.37.111.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS198499 whose prefix no peer sees AS198499 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 86.36.64.0/22 | RIPE | Valid |
| 86.36.68.0/22 | RIPE | Valid |
| 86.36.72.0/22 | RIPE | Valid |
| 86.36.76.0/22 | RIPE | Valid |
| 86.36.80.0/22 | RIPE | Valid |
| 86.36.84.0/22 | RIPE | Valid |
| 86.36.88.0/22 | RIPE | Valid |
| 86.36.92.0/22 | RIPE | Valid |
| 185.37.96.0/24 | RIPE | Valid |
| 185.37.97.0/24 | RIPE | Valid |
| 185.37.98.0/24 | RIPE | Valid |
| 185.37.108.0/23 | RIPE | Valid |
| 185.37.109.0/24 | RIPE | Valid |
| 2a00:f0e0:c::/48 | RIPE | Valid |
| 2a00:f0e0:20::/48 | RIPE | Valid |
| 2a00:f0e0:30::/48 | RIPE | Valid |
| 2a00:f0e0:45::/48 | RIPE | Valid |
| 2a00:f0e0:50::/48 | RIPE | Valid |
| 2a00:f0e0:51::/48 | RIPE | Valid |
| 2a00:f0e0:80::/48 | RIPE | Valid |
| 2a00:f0e0:100::/48 | RIPE | Valid |
| 2a00:f0e0:151::/48 | RIPE | Valid |
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.