bgpreport

Network · data from 2026-11-12

AS266193 AS266193 - Mailbox INTERNET E TELECOMUNICACOES LTDA

Registry name: AS266193 - Mailbox INTERNET E TELECOMUNICACOES LTDA, BR · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 60.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS266193, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266193, 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.
216.98.222.0/24 No ROA Other origin onlycovered by 216.98.220.0/22 672 100% 67
216.98.220.0/24 No ROA Nonecovered by 216.98.220.0/22 671 100% 66
216.98.220.0/22 No ROA Other IRR onlyRADB 672 100% 66
216.98.223.0/24 No ROA Other IRR onlyRADB 672 100% 66
216.98.221.0/24 No ROA Other IRR onlyRADB 671 100% 67
2804:3c24::/32 No ROA Other IRR onlyRADB 632 99% 67

AS-SET

AS266193 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none216.98.222.0/24No ROA covers it. Add a ROA for AS266193, maxLength 24.672 of 673
Route object: none216.98.222.0/24Route objects for it name AS19445. A route object for 216.98.220.0/22 with origin AS266193 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266193 in the RIR database for the space.672 of 673
ROA: none216.98.220.0/24No ROA covers it. Add a ROA for AS266193, maxLength 24.671 of 673
Route object: none216.98.220.0/24No route object for it. A route object for 216.98.220.0/22 with origin AS266193 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266193 in the RIR database for the space.671 of 673
ROA: none216.98.220.0/22No ROA covers it. Add a ROA for AS266193, maxLength 22.672 of 673
Route object: RIR216.98.220.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none216.98.223.0/24No ROA covers it. Add a ROA for AS266193, maxLength 24.672 of 673
Route object: RIR216.98.223.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none216.98.221.0/24No ROA covers it. Add a ROA for AS266193, maxLength 24.671 of 673
Route object: RIR216.98.221.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:3c24::/32No ROA covers it. Add a ROA for AS266193, maxLength 32.632 of 636
Route object: RIR2804:3c24::/32Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

Every route object with origin AS266193 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.