bgpreport

Network · data from 2026-11-12

AS267666 LOG LINK INFORMATICA LTDA - ME

Registry name: AS267666 - LOG LINK INFORMATICA LTDA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267666, 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:4500::/33 Valid Nonecovered by 2804:4500::/32 3 0%low visibility 3
2804:4500:8000::/33 Valid Nonecovered by 2804:4500::/32 3 0%low visibility 3
45.224.208.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
2804:4500::/32 Valid Other IRR onlyRADB, TC 634 100% 67
45.224.208.0/23 Valid Other IRR onlyRADB 10 1%low visibility 8
45.224.210.0/23 Valid Other IRR onlyRADB 10 1%low visibility 8

AS-SET

AS267666'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 8 are in fix.csv.

  • Route object: none2
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2804:4500::/33No route object for it. A route object for 2804:4500::/32 with origin AS267666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267666 in the RIR database for the space.3 of 636
Route object: none2804:4500:8000::/33No route object for it. A route object for 2804:4500::/32 with origin AS267666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267666 in the RIR database for the space.3 of 636
Route object: RIR45.224.208.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:4500::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR45.224.208.0/23Route object only in RADB. Add it in the RIR database for the space.10 of 673
Route object: RIR45.224.210.0/23Route object only in RADB. Add it in the RIR database for the space.10 of 673

Route objects not announced

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

45.224.210.0/24RADBValid
45.224.211.0/24RADBValid

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.