Network · data from 2026-11-12
AS43824 Dataprolinks
Registry name: MASCO-AS Masco Group LLC, LB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43824, 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.
| 185.160.224.0/24 | Valid | Nonecovered by 185.160.224.0/22 | 673 100% |
| 2a0a:c0:ffff::/48 | Valid | Nonecovered by 2a0a:c0::/29 | 635 100% |
| 2a0b:8e80:1::/48 | Valid | None | 634 100% |
| 78.40.176.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.177.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.178.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.179.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.180.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.181.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.182.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.183.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.87.171.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.99.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.99.33.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.99.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.160.225.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.160.226.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.160.227.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.142.87.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a0b:8e80::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS43824'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 12 are in fix.csv.
- Route object: none3
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.160.224.0/24 | No route object for it. A route object for 185.160.224.0/22 with origin AS43824 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43824 in the RIR database for the space. |
| Route object: none | 2a0a:c0:ffff::/48 | No route object for it. A route object for 2a0a:c0::/29 with origin AS43824 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43824 in the RIR database for the space. |
| Route object: none | 2a0b:8e80:1::/48 | No route object for it. Add a route object with origin AS43824 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS43824 whose prefix no peer sees AS43824 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 78.40.176.0/23 | RIPE | No ROA |
| 185.111.160.0/24 | RIPE | Valid |
| 185.111.161.0/24 | RIPE | Valid |
| 185.160.224.0/22 | RIPE | No ROA |
| 185.204.51.0/24 | RIPE | Valid |
| 2a0a:c0::/29 | RIPE | No ROA |
| 2a0a:c0::/48 | RIPE | No ROA |
| 2a0a:c0:1::/48 | RIPE | No ROA |
| 2a0a:c0:2::/48 | RIPE | 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.