bgpreport

Network · data from 2026-11-12

AS267546 Goiás Conect

Registry name: AS267546 - GOIAS CONECT TELECOM EIRELI - ME, BR · PeeringDB

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

Announced routes

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

45.166.212.0/23 Valid Nonecovered by 45.166.212.0/22 672 100% 67
45.166.214.0/23 Valid Nonecovered by 45.166.212.0/22 672 100% 67
191.241.88.0/22 Valid Nonecovered by 191.241.88.0/21 672 100% 67
191.241.92.0/22 Valid Nonecovered by 191.241.88.0/21 672 100% 67
2804:4310::/33 Valid Nonecovered by 2804:4310::/32 636 100% 67
2804:4310:8000::/33 Valid Nonecovered by 2804:4310::/32 636 100% 67
45.166.215.0/24 Valid Nonecovered by 45.166.212.0/22 6 1%low visibility 4
191.241.88.0/24 Valid Nonecovered by 191.241.88.0/21 6 1%low visibility 4
191.241.89.0/24 Valid Nonecovered by 191.241.88.0/21 6 1%low visibility 4
191.241.90.0/24 Valid Nonecovered by 191.241.88.0/21 6 1%low visibility 4
191.241.91.0/24 Valid Nonecovered by 191.241.88.0/21 6 1%low visibility 4
191.241.92.0/24 Valid Nonecovered by 191.241.88.0/21 6 1%low visibility 4
191.241.93.0/24 Valid Nonecovered by 191.241.88.0/21 6 1%low visibility 4
191.241.94.0/24 Valid Nonecovered by 191.241.88.0/21 6 1%low visibility 4
191.241.95.0/24 Valid Nonecovered by 191.241.88.0/21 6 1%low visibility 4
45.70.40.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 672 100% 67
45.166.212.0/22 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
191.241.88.0/21 Valid Other IRR onlyNTTCOM, RADB, TC 672 100% 67
45.70.40.0/23 Valid Other IRR onlyTC 671 100% 67
45.70.42.0/23 Valid Other IRR onlyTC 671 100% 67
2804:4310::/32 Valid Other IRR onlyNTTCOM, RADB, TC 636 100% 67
45.70.40.0/24 Valid Other IRR onlyTC 6 1%low visibility 4
45.70.41.0/24 Valid Other IRR onlyTC 6 1%low visibility 4
45.70.42.0/24 Valid Other IRR onlyTC 6 1%low visibility 4
45.70.43.0/24 Valid Other IRR onlyTC 6 1%low visibility 4

AS-SET

AS267546'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 25 are in fix.csv.

  • Route object: none15
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
Route object: none45.166.212.0/23No route object for it. A route object for 45.166.212.0/22 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.672 of 673
Route object: none45.166.214.0/23No route object for it. A route object for 45.166.212.0/22 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.672 of 673
Route object: none191.241.88.0/22No route object for it. A route object for 191.241.88.0/21 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.672 of 673
Route object: none191.241.92.0/22No route object for it. A route object for 191.241.88.0/21 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.672 of 673
Route object: none2804:4310::/33No route object for it. A route object for 2804:4310::/32 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.636 of 636
Route object: none2804:4310:8000::/33No route object for it. A route object for 2804:4310::/32 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.636 of 636
Route object: none45.166.215.0/24No route object for it. A route object for 45.166.212.0/22 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.6 of 673
Route object: none191.241.88.0/24No route object for it. A route object for 191.241.88.0/21 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.6 of 673
Route object: none191.241.89.0/24No route object for it. A route object for 191.241.88.0/21 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.6 of 673
Route object: none191.241.90.0/24No route object for it. A route object for 191.241.88.0/21 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.6 of 673
Route object: none191.241.91.0/24No route object for it. A route object for 191.241.88.0/21 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.6 of 673
Route object: none191.241.92.0/24No route object for it. A route object for 191.241.88.0/21 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.6 of 673
Route object: none191.241.93.0/24No route object for it. A route object for 191.241.88.0/21 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.6 of 673
Route object: none191.241.94.0/24No route object for it. A route object for 191.241.88.0/21 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.6 of 673
Route object: none191.241.95.0/24No route object for it. A route object for 191.241.88.0/21 with origin AS267546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267546 in the RIR database for the space.6 of 673
Route object: RIR45.70.40.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.166.212.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR191.241.88.0/21Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.70.40.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.70.42.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:4310::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR45.70.40.0/24Route object only in TC. Add it in the RIR database for the space.6 of 673
Route object: RIR45.70.41.0/24Route object only in TC. Add it in the RIR database for the space.6 of 673
Route object: RIR45.70.42.0/24Route object only in TC. Add it in the RIR database for the space.6 of 673
Route object: RIR45.70.43.0/24Route object only in TC. Add it in the RIR database for the space.6 of 673

Route objects not announced

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