Network · data from 2026-11-12
AS16410 DKM3-ARIN - The Reynolds and Reynolds Company
Registry name: DKM3-ARIN - The Reynolds and Reynolds Company, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16410, 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.
| 205.157.193.0/24 | No ROA | Nonecovered by 205.157.192.0/18 | 673 100% |
| 205.157.232.0/23 | No ROA | Nonecovered by 205.157.192.0/18 | 673 100% |
| 205.157.234.0/23 | No ROA | Nonecovered by 205.157.192.0/18 | 673 100% |
| 205.157.204.0/24 | Valid | Nonecovered by 205.157.192.0/18 | 673 100% |
| 205.157.240.0/24 | Valid | Nonecovered by 205.157.192.0/18 | 673 100% |
| 205.157.242.0/24 | Valid | Nonecovered by 205.157.192.0/18 | 673 100% |
| 205.157.244.0/24 | Valid | Nonecovered by 205.157.192.0/18 | 673 100% |
| 205.157.246.0/24 | Valid | Nonecovered by 205.157.192.0/18 | 673 100% |
| 205.157.247.0/24 | Valid | Nonecovered by 205.157.192.0/18 | 673 100% |
| 206.180.2.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.3.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.6.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.10.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.11.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.18.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.19.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.29.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.30.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.36.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.53.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.56.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.60.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 673 100% |
| 206.180.8.0/24 | Valid | Nonecovered by 206.180.0.0/18 | 2 0%low visibility |
| 192.112.245.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 205.157.203.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 205.157.245.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 205.157.248.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 205.157.249.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 205.157.250.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 205.157.251.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 205.157.254.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 205.157.255.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.0.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.4.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.5.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.7.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.12.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.25.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.27.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.28.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.37.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.38.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.39.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.52.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 206.180.55.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
AS16410 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 55 are in fix.csv.
- ROA: none3
- Route object: none23
- Route object: RIR22
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 205.157.193.0/24 | No ROA covers it. Add a ROA for AS16410, maxLength 24. |
| Route object: none | 205.157.193.0/24 | No route object for it. A route object for 205.157.192.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| ROA: none | 205.157.232.0/23 | No ROA covers it. Add a ROA for AS16410, maxLength 23. |
| Route object: none | 205.157.232.0/23 | No route object for it. A route object for 205.157.192.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| ROA: none | 205.157.234.0/23 | No ROA covers it. Add a ROA for AS16410, maxLength 23. |
| Route object: none | 205.157.234.0/23 | No route object for it. A route object for 205.157.192.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 205.157.204.0/24 | No route object for it. A route object for 205.157.192.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 205.157.240.0/24 | No route object for it. A route object for 205.157.192.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 205.157.242.0/24 | No route object for it. A route object for 205.157.192.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 205.157.244.0/24 | No route object for it. A route object for 205.157.192.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 205.157.246.0/24 | No route object for it. A route object for 205.157.192.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 205.157.247.0/24 | No route object for it. A route object for 205.157.192.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.2.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.3.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.6.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.10.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.11.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.18.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.19.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.29.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.30.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.36.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.53.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.56.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.60.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: none | 206.180.8.0/24 | No route object for it. A route object for 206.180.0.0/18 with origin AS16410 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16410 in the RIR database for the space. |
| Route object: RIR | 192.112.245.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.157.203.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.157.245.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.157.248.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.157.249.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.157.250.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.157.251.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.157.254.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.157.255.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.0.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.4.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.5.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.7.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.12.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.25.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.27.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.28.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.37.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.38.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.39.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.52.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.180.55.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16410 whose prefix no peer sees AS16410 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 205.157.192.0/18 | RADB | No ROA |
| 205.157.196.0/24 | RADB | No ROA |
| 205.157.252.0/24 | RADB | No ROA |
| 205.157.253.0/24 | RADB | No ROA |
| 206.180.0.0/18 | RADB | No ROA |
| 206.180.9.0/24 | ARIN | Valid |
| 206.180.40.0/24 | RADB | 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.