bgpreport

Network · data from 2026-11-12

AS264448 NEOLOG TECNOLOGIA LTDA

Registry name: AS264448 - NEOLOG TECNOLOGIA LTDA, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
6IPv6 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
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS264448, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264448, 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.
131.255.28.0/24 Valid Other IRR onlyRADB 671 100% 66
131.255.29.0/24 Valid Other IRR onlyRADB 668 99% 66
131.255.28.0/22 Valid Other IRR onlyRADB 667 99% 66
131.255.28.0/23 Valid Other IRR onlyRADB 664 99% 67
131.255.30.0/23 Valid Other IRR onlyRADB 664 99% 67
2804:1ecc::/34 Valid Other IRR onlyRADB 631 99% 67
2804:1ecc:4000::/34 Valid Other IRR onlyRADB 631 99% 67
2804:1ecc:8000::/34 Valid Other IRR onlyRADB 631 99% 67
2804:1ecc::/32 Valid Other IRR onlyRADB 629 99% 67
2804:1ecc::/33 Valid Other IRR onlyRADB 352 55% 64
2804:1ecc:8000::/33 Valid Other IRR onlyRADB 352 55% 64
131.255.30.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
131.255.31.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS264448'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 13 are in fix.csv.

  • Route object: RIR13
ChangePrefix or setDetailFull-table peers
Route object: RIR131.255.28.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR131.255.29.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR131.255.28.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR131.255.28.0/23Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR131.255.30.0/23Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR2804:1ecc::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:1ecc:4000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:1ecc:8000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:1ecc::/32Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:1ecc::/33Route object only in RADB. Add it in the RIR database for the space.352 of 636
Route object: RIR2804:1ecc:8000::/33Route object only in RADB. Add it in the RIR database for the space.352 of 636
Route object: RIR131.255.30.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR131.255.31.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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