Network · data from 2026-11-12
AS268227 PROTEK INFORMATICA EIRELI
Registry name: AS268227 - PROTEK INFORMATICA EIRELI ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268227, 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.
| 45.236.84.0/23 | No ROA | Nonecovered by 45.236.84.0/22 | 671 100% |
| 45.236.84.0/24 | No ROA | Nonecovered by 45.236.84.0/22 | 668 99% |
| 45.236.85.0/24 | No ROA | Nonecovered by 45.236.84.0/22 | 668 99% |
| 45.236.86.0/24 | No ROA | Nonecovered by 45.236.86.0/23 | 668 99% |
| 45.236.87.0/24 | No ROA | Nonecovered by 45.236.86.0/23 | 668 99% |
| 2804:7054::/32 | No ROA | Other origin only | 630 99% |
| 45.236.84.0/22 | No ROA | Other IRR onlyRADB, TC | 671 100% |
| 45.236.86.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 2804:4de8::/32 | No ROA | Other IRR onlyRADB, TC | 631 99% |
AS-SET
AS268227'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 18 are in fix.csv.
- ROA: none9
- Route object: none6
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.236.84.0/23 | No ROA covers it. Add a ROA for AS268227, maxLength 23. |
| Route object: none | 45.236.84.0/23 | No route object for it. A route object for 45.236.84.0/22 with origin AS268227 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268227 in the RIR database for the space. |
| ROA: none | 45.236.84.0/24 | No ROA covers it. Add a ROA for AS268227, maxLength 24. |
| Route object: none | 45.236.84.0/24 | No route object for it. A route object for 45.236.84.0/22 with origin AS268227 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268227 in the RIR database for the space. |
| ROA: none | 45.236.85.0/24 | No ROA covers it. Add a ROA for AS268227, maxLength 24. |
| Route object: none | 45.236.85.0/24 | No route object for it. A route object for 45.236.84.0/22 with origin AS268227 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268227 in the RIR database for the space. |
| ROA: none | 45.236.86.0/24 | No ROA covers it. Add a ROA for AS268227, maxLength 24. |
| Route object: none | 45.236.86.0/24 | No route object for it. A route object for 45.236.86.0/23 with origin AS268227 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268227 in the RIR database for the space. |
| ROA: none | 45.236.87.0/24 | No ROA covers it. Add a ROA for AS268227, maxLength 24. |
| Route object: none | 45.236.87.0/24 | No route object for it. A route object for 45.236.86.0/23 with origin AS268227 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268227 in the RIR database for the space. |
| ROA: none | 2804:7054::/32 | No ROA covers it. Add a ROA for AS268227, maxLength 32. |
| Route object: none | 2804:7054::/32 | Route objects for it name AS270720. Add a route object with origin AS268227 in the RIR database for the space. |
| ROA: none | 45.236.84.0/22 | No ROA covers it. Add a ROA for AS268227, maxLength 22. |
| Route object: RIR | 45.236.84.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 45.236.86.0/23 | No ROA covers it. Add a ROA for AS268227, maxLength 23. |
| Route object: RIR | 45.236.86.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:4de8::/32 | No ROA covers it. Add a ROA for AS268227, maxLength 32. |
| Route object: RIR | 2804:4de8::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS268227 is announced.
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.