bgpreport

Network · data from 2026-11-12

AS262632 Graja Fibra Telecomunicações Ltda

Registry name: AS262632 - Graja Fibra, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262632, 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:744:1300::/40 Invalid: maxLength Nonecovered by 2804:744::/35 17 3%low visibility 11
177.104.192.0/21 Valid Other IRR onlyTC 669 99% 67
177.104.201.0/24 Valid Other IRR onlyTC 669 99% 67
177.104.202.0/24 Valid Other IRR onlyTC 669 99% 67
177.104.203.0/24 Valid Other IRR onlyTC 669 99% 67
177.104.204.0/24 Valid Other IRR onlyTC 669 99% 67
177.104.205.0/24 Valid Other IRR onlyTC 669 99% 67
177.104.207.0/24 Valid Other IRR onlyTC 669 99% 67
177.104.200.0/24 Valid Other IRR onlyTC 668 99% 67
177.104.206.0/24 Valid Other IRR onlyTC 668 99% 67
2804:744::/35 Valid Other IRR onlyTC 635 100% 67
2804:744:2000::/35 Valid Other IRR onlyTC 635 100% 67
2804:744:4000::/35 Valid Other IRR onlyTC 635 100% 67
2804:744:6000::/35 Valid Other IRR onlyTC 635 100% 67
2804:744:8000::/35 Valid Other IRR onlyTC 635 100% 67
2804:744:a000::/35 Valid Other IRR onlyTC 635 100% 67
2804:744:c000::/35 Valid Other IRR onlyTC 635 100% 67
2804:744:e000::/35 Valid Other IRR onlyTC 635 100% 67
177.104.192.0/20 Valid Other IRR onlyTC 2 0%low visibility 3
177.104.200.0/21 Valid Other IRR onlyTC 2 0%low visibility 3
2804:744::/32 Valid Other IRR onlyRADB, TC 1 0%low visibility 1
177.104.192.0/22 Valid Other IRR onlyTC 0 0%low visibility 1
177.104.196.0/22 Valid Other IRR onlyTC 0 0%low visibility 1
177.104.200.0/22 Valid Other IRR onlyTC 0 0%low visibility 1
177.104.204.0/22 Valid Other IRR onlyTC 0 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS262632: AS262632:AS-GRAJA. 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 (AS262632 isn't in the set, or no route object for AS262632 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 objectsAS262632 in itNot covered
AS262632:AS-GRAJA TC 192227 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 27 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR24
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:744:1300::/40ROA 2804:744::/32 AS262632 has maxLength 35; the route is a /40. Raise the maxLength, or add a ROA for 2804:744:1300::/40.17 of 636
Route object: none2804:744:1300::/40No route object for it. A route object for 2804:744::/35 with origin AS262632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262632 in the RIR database for the space.17 of 636
Route object: RIR177.104.192.0/21Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.104.201.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.104.202.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.104.203.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.104.204.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.104.205.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.104.207.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.104.200.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.104.206.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:744::/35Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:744:2000::/35Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:744:4000::/35Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:744:6000::/35Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:744:8000::/35Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:744:a000::/35Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:744:c000::/35Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:744:e000::/35Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR177.104.192.0/20Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR177.104.200.0/21Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR2804:744::/32Route object only in RADB, TC. Add it in the RIR database for the space.1 of 636
Route object: RIR177.104.192.0/22Route object only in TC. Add it in the RIR database for the space.0 of 673
Route object: RIR177.104.196.0/22Route object only in TC. Add it in the RIR database for the space.0 of 673
Route object: RIR177.104.200.0/22Route object only in TC. Add it in the RIR database for the space.0 of 673
Route object: RIR177.104.204.0/22Route object only in TC. Add it in the RIR database for the space.0 of 673

Route objects not announced

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

177.104.202.0/23TCValid

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.