bgpreport

Network · data from 2026-11-12

AS263255 InfotecNet

Registry name: AS263255 - INFOTECNET ISP LTDA, BR · PeeringDB

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

Announced routes

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

190.180.148.0/23 Valid Other IRR onlyRADB, TC 667 99% 67
190.180.150.0/23 Valid Other IRR onlyTC 667 99% 67
190.180.150.0/24 Valid Other IRR onlyTC 665 99% 67
190.180.151.0/24 Valid Other IRR onlyRADB, TC 665 99% 67
2804:17dc::/33 Valid Other IRR onlyTC 631 99% 67
2804:17dc:8000::/34 Valid Other IRR onlyTC 631 99% 67
2804:17dc:c000::/34 Valid Other IRR onlyTC 631 99% 67
2804:17dc:8000::/33 Valid Other IRR onlyTC 629 99% 67
2804:17dc::/34 Valid Other IRR onlyTC 3 0%low visibility 3

AS-SET

AS263255'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 14 are in fix.csv.

  • Route object: RIR9
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR190.180.148.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR190.180.150.0/23Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR190.180.150.0/24Route object only in TC. Add it in the RIR database for the space.665 of 673
Route object: RIR190.180.151.0/24Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:17dc::/33Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:17dc:8000::/34Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:17dc:c000::/34Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:17dc:8000::/33Route object only in TC. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:17dc::/34Route object only in TC. Add it in the RIR database for the space.3 of 636

Route objects not announced

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

190.180.148.0/22RADB, TCValid
190.180.148.0/24TCValid
190.180.149.0/24RADB, TCValid
2804:17dc::/32RADB, TCValid
2804:17dc:4000::/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.