bgpreport

Network · data from 2026-11-12

AS266211 J. TEIXEIRA DOS SANTOS - ME

Registry name: AS266211 - GERACAO NET, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266211, 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.229.164.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
192.144.100.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
200.0.8.0/21 Valid Other IRR onlyTC 671 100% 67
200.0.8.0/22 Valid Other IRR onlyTC 671 100% 67
200.0.12.0/22 Valid Other IRR onlyTC 671 100% 67
2804:3c70::/32 Valid Other IRR onlyRADB, TC 632 99% 67
2804:3c70::/33 Valid Other IRR onlyTC 350 55% 65
2804:3c70:8000::/33 Valid Other IRR onlyTC 350 55% 65
45.229.164.0/23 Valid Other IRR onlyTC 206 31% 56
45.229.166.0/23 Valid Other IRR onlyTC 206 31% 56
192.144.100.0/23 Valid Other IRR onlyRADB, TC 206 31% 56
200.0.8.0/23 Valid Other IRR onlyTC 206 31% 56
200.0.10.0/23 Valid Other IRR onlyTC 206 31% 56
200.0.12.0/23 Valid Other IRR onlyTC 206 31% 56
200.0.14.0/23 Valid Other IRR onlyTC 206 31% 56
192.144.102.0/23 Valid Other IRR onlyRADB, TC 205 30% 56

AS-SET

PeeringDB's irr_as_set for AS266211: AS266211:AS-GERACAONET. 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 (AS266211 isn't in the set, or no route object for AS266211 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 objectsAS266211 in itNot covered
AS266211:AS-GERACAONET NTTCOM 101141 Yes 0
TC (also) 72119 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 36 are in fix.csv.

  • Route object: RIR16
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
Route object: RIR45.229.164.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR192.144.100.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.0.8.0/21Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.0.8.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.0.12.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:3c70::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:3c70::/33Route object only in TC. Add it in the RIR database for the space.350 of 636
Route object: RIR2804:3c70:8000::/33Route object only in TC. Add it in the RIR database for the space.350 of 636
Route object: RIR45.229.164.0/23Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR45.229.166.0/23Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR192.144.100.0/23Route object only in RADB, TC. Add it in the RIR database for the space.206 of 673
Route object: RIR200.0.8.0/23Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR200.0.10.0/23Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR200.0.12.0/23Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR200.0.14.0/23Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR192.144.102.0/23Route object only in RADB, TC. Add it in the RIR database for the space.205 of 673

Route objects not announced

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

45.229.164.0/24TCValid
45.229.165.0/24TCValid
45.229.166.0/24TCValid
45.229.167.0/24TCValid
192.144.100.0/24RADB, TCValid
192.144.101.0/24RADB, TCValid
192.144.102.0/24RADB, TCValid
192.144.103.0/24RADB, TCValid
200.0.8.0/24TCValid
200.0.9.0/24TCValid
200.0.10.0/24TCValid
200.0.11.0/24TCValid
200.0.12.0/24TCValid
200.0.13.0/24TCValid
200.0.14.0/24TCValid
200.0.15.0/24TCValid
2804:3c70::/34TCValid
2804:3c70:4000::/34TCValid
2804:3c70:8000::/34TCValid
2804:3c70:c000::/34TCValid

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.