Network · data from 2026-11-12
AS267919 AS267919 - NET&COM LTDA.
Registry name: AS267919 - NET&COM LTDA., CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267919, 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.
| 38.252.206.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 45.179.201.0/24 | Valid | Nonecovered by 45.179.200.0/23 | 673 100% |
| 45.179.200.0/24 | Valid | Nonecovered by 45.179.200.0/23 | 670 100% |
| 45.179.203.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 2803:ee60:30::/44 | Valid | RIR databaseLACNIC | 635 100% |
| 2803:ee60:40::/44 | Valid | RIR databaseLACNIC | 635 100% |
| 2803:ee60:50::/44 | Valid | RIR databaseLACNIC | 635 100% |
| 2803:ee60:a0::/44 | Valid | RIR databaseLACNIC, RADB | 635 100% |
| 2803:ee60:b0::/44 | Valid | RIR databaseLACNIC, RADB | 635 100% |
| 2803:ee60:c0::/44 | Valid | RIR databaseLACNIC, RADB | 635 100% |
AS-SET
AS267919 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 9 are in fix.csv.
- ROA: origin1
- Route object: none3
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 38.252.206.0/24 | ROAs covering it name AS275777, not AS267919. If AS267919 should announce it, add a ROA for AS267919. |
| Route object: none | 38.252.206.0/24 | Route objects for it name AS275777. Add a route object with origin AS267919 in the RIR database for the space. |
| Route object: none | 45.179.201.0/24 | No route object for it. A route object for 45.179.200.0/23 with origin AS267919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267919 in the RIR database for the space. |
| Route object: none | 45.179.200.0/24 | No route object for it. A route object for 45.179.200.0/23 with origin AS267919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267919 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267919 whose prefix no peer sees AS267919 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.179.200.0/23 | LACNIC | Valid |
| 2803:ee60:10::/44 | LACNIC, RADB | Valid |
| 2803:ee60:20::/44 | LACNIC | Valid |
| 2803:ee60:100::/43 | LACNIC | Valid |
| 2803:ee60:120::/44 | LACNIC | 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.