bgpreport

Network · data from 2026-11-12

AS61660 CRAPAC SERVICOS DE TELECOMUNICACOES LTDA - ME

Registry name: AS61660 - CRAPAC SERVICOS DE TELECOMUNICACOES LTDA - ME, BR · PeeringDB

14IPv4 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
0Route objects not announced registered with origin AS61660, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61660, 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.
131.108.44.0/22 Valid Other IRR onlyTC 671 100% 67
138.185.100.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
2804:1c88::/32 Valid Other IRR onlyRADB, TC 631 99% 67
2804:1c88::/33 Valid Other IRR onlyRADB, TC 330 52% 65
2804:1c88:8000::/33 Valid Other IRR onlyRADB, TC 330 52% 65
131.108.44.0/23 Valid Other IRR onlyRADB, TC 150 22% 51
131.108.44.0/24 Valid Other IRR onlyRADB, TC 150 22% 51
131.108.45.0/24 Valid Other IRR onlyRADB, TC 150 22% 51
131.108.46.0/23 Valid Other IRR onlyRADB, TC 150 22% 51
131.108.47.0/24 Valid Other IRR onlyRADB, TC 150 22% 51
138.185.100.0/23 Valid Other IRR onlyRADB, TC 150 22% 51
138.185.100.0/24 Valid Other IRR onlyRADB, TC 150 22% 51
138.185.101.0/24 Valid Other IRR onlyRADB, TC 150 22% 51
138.185.102.0/23 Valid Other IRR onlyRADB, TC 150 22% 51
138.185.102.0/24 Valid Other IRR onlyRADB, TC 150 22% 51
138.185.103.0/24 Valid Other IRR onlyRADB, TC 150 22% 51
131.108.46.0/24 Valid Other IRR onlyRADB, TC 148 22% 51

AS-SET

PeeringDB's irr_as_set for AS61660: TC::AS61660. 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 (AS61660 isn't in the set, or no route object for AS61660 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 objectsAS61660 in itNot covered
TC::AS61660 A single AS number, not a set: AS61660 (this network), 17 route objects.

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

  • Route object: RIR17
ChangePrefix or setDetailFull-table peers
Route object: RIR131.108.44.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.185.100.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:1c88::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:1c88::/33Route object only in RADB, TC. Add it in the RIR database for the space.330 of 636
Route object: RIR2804:1c88:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.330 of 636
Route object: RIR131.108.44.0/23Route object only in RADB, TC. Add it in the RIR database for the space.150 of 673
Route object: RIR131.108.44.0/24Route object only in RADB, TC. Add it in the RIR database for the space.150 of 673
Route object: RIR131.108.45.0/24Route object only in RADB, TC. Add it in the RIR database for the space.150 of 673
Route object: RIR131.108.46.0/23Route object only in RADB, TC. Add it in the RIR database for the space.150 of 673
Route object: RIR131.108.47.0/24Route object only in RADB, TC. Add it in the RIR database for the space.150 of 673
Route object: RIR138.185.100.0/23Route object only in RADB, TC. Add it in the RIR database for the space.150 of 673
Route object: RIR138.185.100.0/24Route object only in RADB, TC. Add it in the RIR database for the space.150 of 673
Route object: RIR138.185.101.0/24Route object only in RADB, TC. Add it in the RIR database for the space.150 of 673
Route object: RIR138.185.102.0/23Route object only in RADB, TC. Add it in the RIR database for the space.150 of 673
Route object: RIR138.185.102.0/24Route object only in RADB, TC. Add it in the RIR database for the space.150 of 673
Route object: RIR138.185.103.0/24Route object only in RADB, TC. Add it in the RIR database for the space.150 of 673
Route object: RIR131.108.46.0/24Route object only in RADB, TC. Add it in the RIR database for the space.148 of 673

Route objects not announced

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