bgpreport

Network · data from 2026-11-12

AS268281 SUPERA INFORMATICA LTDA

Registry name: AS268281 - SUPERA INFORMATICA LTDA, BR · PeeringDB

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

Announced routes

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

2804:4ec4::/38 Valid Nonecovered by 2804:4ec4::/34 630 99% 67
2804:4ec4:400::/38 Valid Nonecovered by 2804:4ec4::/34 630 99% 67
2804:4ec4:800::/38 Valid Nonecovered by 2804:4ec4::/34 630 99% 67
45.237.141.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
45.237.142.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
45.237.143.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
45.237.140.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
45.237.140.0/22 Valid Other IRR onlyALTDB, NTTCOM, RADB, TC 668 99% 67
2804:4ec4::/32 Valid Other IRR onlyNTTCOM, RADB, TC 629 99% 67

AS-SET

AS268281'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.

  • Route object: none3
  • Route object: RIR6
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none2804:4ec4::/38No route object for it. A route object for 2804:4ec4::/34 with origin AS268281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268281 in the RIR database for the space.630 of 636
Route object: none2804:4ec4:400::/38No route object for it. A route object for 2804:4ec4::/34 with origin AS268281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268281 in the RIR database for the space.630 of 636
Route object: none2804:4ec4:800::/38No route object for it. A route object for 2804:4ec4::/34 with origin AS268281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268281 in the RIR database for the space.630 of 636
Route object: RIR45.237.141.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.237.142.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.237.143.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.237.140.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.237.140.0/22Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:4ec4::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.629 of 636

Route objects not announced

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

40.237.140.0/22RADBNo ROA
45.237.140.0/23TCValid
45.237.142.0/23TCValid
2804:4ec4::/33TCValid
2804:4ec4::/34TCValid
2804:4ec4:4000::/34TCValid
2804:4ec4:8000::/33TCValid
2804:4ec4:8000::/34TCValid
2804:4ec4:c000::/34TCValid

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.