bgpreport

Network · data from 2026-11-12

AS265061 GC Net Provedor

Registry name: AS265061 - MIRIANE ARAUJO LIMA DE OLIVEIRA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265061, 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:3230:802d::/48 Valid Nonecovered by 2804:3230::/32 634 100% 67
2804:3230:8031::/48 Valid Nonecovered by 2804:3230::/32 634 100% 67
2804:3230:8033::/48 Valid Nonecovered by 2804:3230::/32 633 100% 67
2804:3230:8000::/33 Valid Nonecovered by 2804:3230::/32 401 63% 66
2804:3230::/34 Valid Nonecovered by 2804:3230::/33 35 6%low visibility 14
2804:3230:4000::/34 Valid Nonecovered by 2804:3230::/33 35 6%low visibility 14
2804:3230:8000::/34 Valid Nonecovered by 2804:3230::/32 35 6%low visibility 14
170.231.56.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
2804:3230::/32 Valid Other IRR onlyRADB 635 100% 67
2804:3230::/33 Valid Other IRR onlyRADB 401 63% 66
170.231.56.0/23 Valid Other IRR onlyRADB, TC 202 30% 56
170.231.58.0/23 Valid Other IRR onlyRADB, TC 202 30% 56
170.231.57.0/24 Valid Other IRR onlyTC 155 23% 51
170.231.58.0/24 Valid Other IRR onlyTC 155 23% 51
170.231.56.0/24 Valid Other IRR onlyTC 127 19% 44
170.231.59.0/24 Valid Other IRR onlyTC 127 19% 44

AS-SET

PeeringDB's irr_as_set for AS265061: AS-GCNETPROVEDOR. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS265061 isn't in the set, or no route object for AS265061 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS265061 in itNot covered
AS-GCNETPROVEDOR ALTDB 753763 Yes 0
TC (also) 393313 Yes 0

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 16 are in fix.csv.

  • Route object: none7
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
Route object: none2804:3230:802d::/48No route object for it. A route object for 2804:3230::/32 with origin AS265061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265061 in the RIR database for the space.634 of 636
Route object: none2804:3230:8031::/48No route object for it. A route object for 2804:3230::/32 with origin AS265061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265061 in the RIR database for the space.634 of 636
Route object: none2804:3230:8033::/48No route object for it. A route object for 2804:3230::/32 with origin AS265061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265061 in the RIR database for the space.633 of 636
Route object: none2804:3230:8000::/33No route object for it. A route object for 2804:3230::/32 with origin AS265061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265061 in the RIR database for the space.401 of 636
Route object: none2804:3230::/34No route object for it. A route object for 2804:3230::/33 with origin AS265061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265061 in the RIR database for the space.35 of 636
Route object: none2804:3230:4000::/34No route object for it. A route object for 2804:3230::/33 with origin AS265061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265061 in the RIR database for the space.35 of 636
Route object: none2804:3230:8000::/34No route object for it. A route object for 2804:3230::/32 with origin AS265061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265061 in the RIR database for the space.35 of 636
Route object: RIR170.231.56.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:3230::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3230::/33Route object only in RADB. Add it in the RIR database for the space.401 of 636
Route object: RIR170.231.56.0/23Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673
Route object: RIR170.231.58.0/23Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673
Route object: RIR170.231.57.0/24Route object only in TC. Add it in the RIR database for the space.155 of 673
Route object: RIR170.231.58.0/24Route object only in TC. Add it in the RIR database for the space.155 of 673
Route object: RIR170.231.56.0/24Route object only in TC. Add it in the RIR database for the space.127 of 673
Route object: RIR170.231.59.0/24Route object only in TC. Add it in the RIR database for the space.127 of 673

Route objects not announced

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