bgpreport

Network · data from 2026-11-12

AS266170 FUTURETEC TELECOM

Registry name: AS266170 - FUTURETEC TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266170, 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:3bc8:12e::/48 Valid Nonecovered by 2804:3bc8::/33 635 100% 67
2804:3bc8:12f::/48 Valid Nonecovered by 2804:3bc8::/33 635 100% 67
45.6.176.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
45.6.176.0/23 Valid Other IRR onlyTC 667 99% 67
45.6.178.0/23 Valid Other IRR onlyTC 667 99% 67
45.6.176.0/24 Valid Other IRR onlyTC 666 99% 67
45.6.177.0/24 Valid Other IRR onlyTC 666 99% 67
45.6.178.0/24 Valid Other IRR onlyTC 666 99% 67
45.6.179.0/24 Valid Other IRR onlyTC 666 99% 67
2804:3bc8::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:3bc8::/33 Valid Other IRR onlyTC 635 100% 67
2804:3bc8:8000::/33 Valid Other IRR onlyTC 635 100% 67

AS-SET

AS266170'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 12 are in fix.csv.

  • Route object: none2
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
Route object: none2804:3bc8:12e::/48No route object for it. A route object for 2804:3bc8::/33 with origin AS266170 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266170 in the RIR database for the space.635 of 636
Route object: none2804:3bc8:12f::/48No route object for it. A route object for 2804:3bc8::/33 with origin AS266170 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266170 in the RIR database for the space.635 of 636
Route object: RIR45.6.176.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.6.176.0/23Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.6.178.0/23Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.6.176.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR45.6.177.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR45.6.178.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR45.6.179.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:3bc8::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3bc8::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3bc8:8000::/33Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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