Network · data from 2026-11-12
AS35937 DATABANK-MARQUISNET - MarquisNet
Registry name: DATABANK-MARQUISNET - MarquisNet, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35937, 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.
| 199.102.48.0/22 | No ROA | None | 673 100% |
| 208.110.171.0/24 | No ROA | Nonecovered by 208.110.160.0/20 | 673 100% |
| 192.103.252.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 204.15.164.0/22 | No ROA | Other IRR onlyALTDB | 673 100% |
| 208.65.156.0/22 | No ROA | Other IRR onlyALTDB | 673 100% |
| 208.67.184.0/21 | No ROA | Other IRR onlyALTDB | 673 100% |
| 208.72.240.0/21 | No ROA | Other IRR onlyALTDB | 673 100% |
| 208.110.160.0/20 | No ROA | Other IRR onlyALTDB, RADB | 673 100% |
| 2607:ffd0:5::/48 | No ROA | Other IRR onlyRADB | 635 100% |
| 207.34.38.0/24 | No ROA | Other IRR onlyRADB | 299 44% |
AS-SET
AS35937 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 25 are in fix.csv.
- ROA: none10
- Route object: none2
- Route object: RIR8
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.102.48.0/22 | No ROA covers it. Add a ROA for AS35937, maxLength 22. |
| Route object: none | 199.102.48.0/22 | No route object for it. Add a route object with origin AS35937 in the RIR database for the space. |
| ROA: none | 208.110.171.0/24 | No ROA covers it. Add a ROA for AS35937, maxLength 24. |
| Route object: none | 208.110.171.0/24 | No route object for it. A route object for 208.110.160.0/20 with origin AS35937 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35937 in the RIR database for the space. |
| ROA: none | 192.103.252.0/24 | No ROA covers it. Add a ROA for AS35937, maxLength 24. |
| Route object: RIR | 192.103.252.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 204.15.164.0/22 | No ROA covers it. Add a ROA for AS35937, maxLength 22. |
| Route object: RIR | 204.15.164.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 208.65.156.0/22 | No ROA covers it. Add a ROA for AS35937, maxLength 22. |
| Route object: RIR | 208.65.156.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 208.67.184.0/21 | No ROA covers it. Add a ROA for AS35937, maxLength 21. |
| Route object: RIR | 208.67.184.0/21 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 208.72.240.0/21 | No ROA covers it. Add a ROA for AS35937, maxLength 21. |
| Route object: RIR | 208.72.240.0/21 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 208.110.160.0/20 | No ROA covers it. Add a ROA for AS35937, maxLength 20. |
| Route object: RIR | 208.110.160.0/20 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 2607:ffd0:5::/48 | No ROA covers it. Add a ROA for AS35937, maxLength 48. |
| Route object: RIR | 2607:ffd0:5::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 207.34.38.0/24 | No ROA covers it. Add a ROA for AS35937, maxLength 24. |
| Route object: RIR | 207.34.38.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS35937 whose prefix no peer sees AS35937 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 24.234.176.0/22 | ALTDB | No ROA |
| 66.33.62.0/24 | RADB | No ROA |
| 66.33.64.0/24 | RADB | No ROA |
| 66.33.66.0/24 | RADB | No ROA |
| 209.223.136.0/21 | ALTDB | No ROA |
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.