bgpreport

Network · data from 2026-11-12

AS263997 BITMAIL SERVICOS DE INFORMATICA

Registry name: AS263997 - BITMAIL SERVICOS DE INFORMATICA LTDA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263997, 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.

143.0.52.0/24 No ROA Other IRR onlyRADB 670 100% 66
143.0.54.0/23 No ROA Other IRR onlyRADB 670 100% 67
143.0.54.0/24 No ROA Other IRR onlyRADB 670 100% 66
143.0.55.0/24 No ROA Other IRR onlyRADB 669 99% 66
2804:2918::/34 No ROA Other IRR onlyRADB 634 100% 67
2804:2918:4000::/34 No ROA Other IRR onlyRADB 634 100% 67
2804:2918:8000::/34 No ROA Other IRR onlyRADB 634 100% 67
2804:2918::/33 No ROA Other IRR onlyRADB 335 53% 65

AS-SET

AS263997'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 21 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none143.0.52.0/24No ROA covers it. Add a ROA for AS263997, maxLength 24.670 of 673
Route object: RIR143.0.52.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none143.0.54.0/23No ROA covers it. Add a ROA for AS263997, maxLength 23.670 of 673
Route object: RIR143.0.54.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none143.0.54.0/24No ROA covers it. Add a ROA for AS263997, maxLength 24.670 of 673
Route object: RIR143.0.54.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none143.0.55.0/24No ROA covers it. Add a ROA for AS263997, maxLength 24.669 of 673
Route object: RIR143.0.55.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:2918::/34No ROA covers it. Add a ROA for AS263997, maxLength 34.634 of 636
Route object: RIR2804:2918::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:2918:4000::/34No ROA covers it. Add a ROA for AS263997, maxLength 34.634 of 636
Route object: RIR2804:2918:4000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:2918:8000::/34No ROA covers it. Add a ROA for AS263997, maxLength 34.634 of 636
Route object: RIR2804:2918:8000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:2918::/33No ROA covers it. Add a ROA for AS263997, maxLength 33.335 of 636
Route object: RIR2804:2918::/33Route object only in RADB. Add it in the RIR database for the space.335 of 636

Route objects not announced

Route objects with origin AS263997 whose prefix no peer sees AS263997 announce. Many are kept on purpose (backup routes, space announced only in some places).

143.0.52.0/22RADB, TCNo ROA
143.0.52.0/23RADBNo ROA
143.0.53.0/24RADBNo ROA
2804:2918::/32RADB, TCNo ROA
2804:2d20::/32RADBNo 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.