bgpreport

Network · data from 2026-11-12

AS263538 TOC INFORMATICA LTDA

Registry name: AS263538 - 1TOC INFORMATICA LTDA, BR · PeeringDB

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

Announced routes

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

191.5.162.0/24 Valid Nonecovered by 191.5.160.0/22 671 100% 66
191.5.161.0/24 Valid Nonecovered by 191.5.160.0/22 668 99% 66
191.5.163.0/24 Valid Nonecovered by 191.5.160.0/22 668 99% 66
191.5.160.0/23 Valid Nonecovered by 191.5.160.0/22 667 99% 66
191.5.160.0/24 Valid Nonecovered by 191.5.160.0/22 667 99% 66
191.5.160.0/22 Valid Other IRR onlyRADB 667 99% 66

AS-SET

AS263538'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 9 are in fix.csv.

  • Route object: none5
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none191.5.162.0/24No route object for it. A route object for 191.5.160.0/22 with origin AS263538 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263538 in the RIR database for the space.671 of 673
Route object: none191.5.161.0/24No route object for it. A route object for 191.5.160.0/22 with origin AS263538 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263538 in the RIR database for the space.668 of 673
Route object: none191.5.163.0/24No route object for it. A route object for 191.5.160.0/22 with origin AS263538 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263538 in the RIR database for the space.668 of 673
Route object: none191.5.160.0/23No route object for it. A route object for 191.5.160.0/22 with origin AS263538 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263538 in the RIR database for the space.667 of 673
Route object: none191.5.160.0/24No route object for it. A route object for 191.5.160.0/22 with origin AS263538 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263538 in the RIR database for the space.667 of 673
Route object: RIR191.5.160.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

2804:1390::/32RADBValid
2804:1390::/33RADBValid
2804:1390:8000::/33RADBValid

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.