Network · data from 2026-11-12
AS203156 Relayify-LLC Relayify LLC
Registry name: Relayify-LLC Relayify LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS203156, 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.
| 82.26.71.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 166.0.10.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 178.83.36.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 178.83.56.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 188.137.159.0/24 | Valid | None | 672 100% |
| 87.82.220.0/24 | Valid | Nonecovered by 87.82.220.0/22 | 670 100% |
| 87.82.221.0/24 | Valid | Nonecovered by 87.82.220.0/22 | 670 100% |
| 87.82.222.0/24 | Valid | Nonecovered by 87.82.220.0/22 | 670 100% |
| 87.82.223.0/24 | Valid | Nonecovered by 87.82.220.0/22 | 670 100% |
| 89.167.176.0/24 | Valid | Nonecovered by 89.167.176.0/22 | 670 100% |
| 89.167.177.0/24 | Valid | Nonecovered by 89.167.176.0/22 | 670 100% |
| 89.167.178.0/24 | Valid | Nonecovered by 89.167.176.0/22 | 670 100% |
| 89.167.179.0/24 | Valid | Nonecovered by 89.167.176.0/22 | 670 100% |
| 89.167.214.0/24 | Valid | Nonecovered by 89.167.214.0/23 | 670 100% |
| 89.167.215.0/24 | Valid | Nonecovered by 89.167.214.0/23 | 670 100% |
| 169.40.76.0/24 | Valid | Nonecovered by 169.40.76.0/22 | 668 99% |
| 169.40.77.0/24 | Valid | Nonecovered by 169.40.76.0/22 | 668 99% |
| 169.40.78.0/24 | Valid | Nonecovered by 169.40.76.0/22 | 668 99% |
| 169.40.79.0/24 | Valid | Nonecovered by 169.40.76.0/22 | 668 99% |
| 178.83.48.0/24 | Valid | Nonecovered by 178.83.48.0/23 | 668 99% |
| 178.83.49.0/24 | Valid | Nonecovered by 178.83.48.0/23 | 668 99% |
| 187.14.156.0/24 | Valid | Nonecovered by 187.14.156.0/22 | 668 99% |
| 187.14.157.0/24 | Valid | Nonecovered by 187.14.156.0/22 | 668 99% |
| 187.14.158.0/24 | Valid | Nonecovered by 187.14.156.0/22 | 668 99% |
| 187.14.159.0/24 | Valid | Nonecovered by 187.14.156.0/22 | 668 99% |
| 189.12.152.0/24 | Valid | Nonecovered by 189.12.152.0/22 | 668 99% |
| 189.12.153.0/24 | Valid | Nonecovered by 189.12.152.0/22 | 668 99% |
| 189.12.154.0/24 | Valid | Nonecovered by 189.12.152.0/22 | 668 99% |
| 189.12.155.0/24 | Valid | Nonecovered by 189.12.152.0/22 | 668 99% |
| 200.138.20.0/24 | Valid | Nonecovered by 200.138.20.0/22 | 667 99% |
| 200.138.21.0/24 | Valid | Nonecovered by 200.138.20.0/22 | 667 99% |
| 200.138.22.0/24 | Valid | Nonecovered by 200.138.20.0/22 | 667 99% |
| 200.138.23.0/24 | Valid | Nonecovered by 200.138.20.0/22 | 667 99% |
| 2a03:ecc0::/29 | Valid | None | 632 99% |
| 103.86.36.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 83.245.71.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 102.212.6.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 216.75.150.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 151.243.149.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.247.230.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 62.105.194.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 83.245.65.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 92.50.3.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 128.65.160.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 128.65.163.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 151.246.142.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 151.247.224.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 217.216.228.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 217.216.236.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 217.216.253.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
AS-SET
AS203156 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 54 are in fix.csv.
- ROA: origin4
- Route object: none34
- Route object: RIR4
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 82.26.71.0/24 | ROAs covering it name AS200169, not AS203156. If AS203156 should announce it, add a ROA for AS203156. |
| Route object: none | 82.26.71.0/24 | Route objects for it name AS200169. Add a route object with origin AS203156 in the RIR database for the space. |
| ROA: origin | 166.0.10.0/24 | ROAs covering it name AS6079, not AS203156. If AS203156 should announce it, add a ROA for AS203156. |
| Route object: none | 166.0.10.0/24 | Route objects for it name AS6079. Add a route object with origin AS203156 in the RIR database for the space. |
| ROA: origin | 178.83.36.0/24 | ROAs covering it name AS834, not AS203156. If AS203156 should announce it, add a ROA for AS203156. |
| Route object: none | 178.83.36.0/24 | Route objects for it name AS834. Add a route object with origin AS203156 in the RIR database for the space. |
| ROA: origin | 178.83.56.0/24 | ROAs covering it name AS834, not AS203156. If AS203156 should announce it, add a ROA for AS203156. |
| Route object: none | 178.83.56.0/24 | Route objects for it name AS834. Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 188.137.159.0/24 | No route object for it. Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 87.82.220.0/24 | No route object for it. A route object for 87.82.220.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 87.82.221.0/24 | No route object for it. A route object for 87.82.220.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 87.82.222.0/24 | No route object for it. A route object for 87.82.220.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 87.82.223.0/24 | No route object for it. A route object for 87.82.220.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 89.167.176.0/24 | No route object for it. A route object for 89.167.176.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 89.167.177.0/24 | No route object for it. A route object for 89.167.176.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 89.167.178.0/24 | No route object for it. A route object for 89.167.176.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 89.167.179.0/24 | No route object for it. A route object for 89.167.176.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 89.167.214.0/24 | No route object for it. A route object for 89.167.214.0/23 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 89.167.215.0/24 | No route object for it. A route object for 89.167.214.0/23 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 169.40.76.0/24 | No route object for it. A route object for 169.40.76.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 169.40.77.0/24 | No route object for it. A route object for 169.40.76.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 169.40.78.0/24 | No route object for it. A route object for 169.40.76.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 169.40.79.0/24 | No route object for it. A route object for 169.40.76.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 178.83.48.0/24 | No route object for it. A route object for 178.83.48.0/23 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 178.83.49.0/24 | No route object for it. A route object for 178.83.48.0/23 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 187.14.156.0/24 | No route object for it. A route object for 187.14.156.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 187.14.157.0/24 | No route object for it. A route object for 187.14.156.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 187.14.158.0/24 | No route object for it. A route object for 187.14.156.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 187.14.159.0/24 | No route object for it. A route object for 187.14.156.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 189.12.152.0/24 | No route object for it. A route object for 189.12.152.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 189.12.153.0/24 | No route object for it. A route object for 189.12.152.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 189.12.154.0/24 | No route object for it. A route object for 189.12.152.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 189.12.155.0/24 | No route object for it. A route object for 189.12.152.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 200.138.20.0/24 | No route object for it. A route object for 200.138.20.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 200.138.21.0/24 | No route object for it. A route object for 200.138.20.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 200.138.22.0/24 | No route object for it. A route object for 200.138.20.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 200.138.23.0/24 | No route object for it. A route object for 200.138.20.0/22 with origin AS203156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: none | 2a03:ecc0::/29 | No route object for it. Add a route object with origin AS203156 in the RIR database for the space. |
| Route object: RIR | 103.86.36.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 83.245.71.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 102.212.6.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 216.75.150.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS203156 whose prefix no peer sees AS203156 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.152.217.0/24 | RADB | Valid |
| 82.153.184.0/24 | RADB | Valid |
| 87.82.220.0/22 | RADB | Valid |
| 89.167.176.0/22 | RADB | Valid |
| 89.167.214.0/23 | RADB | Valid |
| 169.40.76.0/22 | RADB, RIPE | Valid |
| 178.83.48.0/23 | RADB, RIPE | Valid |
| 178.239.123.0/24 | RADB, RIPE | Valid |
| 187.14.156.0/22 | RADB, RIPE | Valid |
| 189.12.152.0/22 | RADB, RIPE | Valid |
| 200.138.20.0/22 | RADB, RIPE | Valid |
| 212.189.70.0/23 | RADB | 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.