Network · data from 2026-11-12
AS61888 GFT COMERCIO DE TELEFONIA E COMUNICACAO
Registry name: AS61888 - GFT COMERCIO DE TELEFONIA E COMUNICACAO LTDA, BR · PeeringDB
14IPv4 routes
100.0% RPKI valid · 100.0% with a route object
24IPv6 routes
100.0% RPKI valid · 83.3% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
4 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
1Route objects not announced
registered with origin AS61888, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS61888, 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:e60:1c::/48 | Valid | Nonecovered by 2804:e60::/33 | 633 100% |
| 2804:e60:1a::/48 | Valid | Nonecovered by 2804:e60::/33 | 632 99% |
| 2804:e60:1b::/48 | Valid | Nonecovered by 2804:e60::/33 | 632 99% |
| 2804:e60:1d::/48 | Valid | Nonecovered by 2804:e60::/33 | 632 99% |
| 186.235.184.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 186.235.184.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 186.235.184.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 186.235.186.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 186.235.186.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 186.235.188.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 186.235.188.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 186.235.190.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 186.235.185.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 186.235.187.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 186.235.188.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 186.235.189.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 186.235.190.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 186.235.191.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 2804:e60::/32 | Valid | Other IRR onlyRADB, TC | 633 100% |
| 2804:e60::/33 | Valid | Other IRR onlyRADB, TC | 633 100% |
| 2804:e60:11::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:e60:17::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:e60:18::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:e60:19::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:e60:300::/43 | Valid | Other IRR onlyTC | 633 100% |
| 2804:e60:8000::/33 | Valid | Other IRR onlyRADB, TC | 633 100% |
| 2804:e60:10::/48 | Valid | Other IRR onlyTC | 632 99% |
| 2804:e60:12::/48 | Valid | Other IRR onlyTC | 632 99% |
| 2804:e60:13::/48 | Valid | Other IRR onlyTC | 632 99% |
| 2804:e60:14::/48 | Valid | Other IRR onlyTC | 632 99% |
| 2804:e60:15::/48 | Valid | Other IRR onlyTC | 632 99% |
| 2804:e60:16::/48 | Valid | Other IRR onlyTC | 632 99% |
| 2804:e60:100::/40 | Valid | Other IRR onlyTC | 632 99% |
| 2804:e60:200::/40 | Valid | Other IRR onlyTC | 632 99% |
| 2804:e60:320::/44 | Valid | Other IRR onlyTC | 632 99% |
| 2804:e60:fa00::/40 | Valid | Other IRR onlyTC | 632 99% |
| 2804:e60:face::/48 | Valid | Other IRR onlyTC | 632 99% |
| 2804:e60:ffff::/48 | Valid | Other IRR onlyTC | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS61888: AS61888:AS-ANNOUNCEMENTS. 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 (AS61888 isn't in the set, or no route object for AS61888 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.
| Name | Database | ASNs | Sets | AS61888 in it | Not covered |
|---|---|---|---|---|---|
| AS61888:AS-ANNOUNCEMENTS | TC | 3 | 2 | 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 39 are in fix.csv.
- Route object: none4
- Route object: RIR34
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:e60:1c::/48 | No route object for it. A route object for 2804:e60::/33 with origin AS61888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61888 in the RIR database for the space. |
| Route object: none | 2804:e60:1a::/48 | No route object for it. A route object for 2804:e60::/33 with origin AS61888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61888 in the RIR database for the space. |
| Route object: none | 2804:e60:1b::/48 | No route object for it. A route object for 2804:e60::/33 with origin AS61888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61888 in the RIR database for the space. |
| Route object: none | 2804:e60:1d::/48 | No route object for it. A route object for 2804:e60::/33 with origin AS61888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61888 in the RIR database for the space. |
| Route object: RIR | 186.235.184.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.184.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.184.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.186.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.186.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.188.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.188.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.190.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.185.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.187.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.188.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.189.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.190.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.235.191.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:11::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:17::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:18::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:19::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:300::/43 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:8000::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:10::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:12::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:13::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:14::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:15::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:16::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:100::/40 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:200::/40 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:320::/44 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:fa00::/40 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:face::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:e60:ffff::/48 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61888 whose prefix no peer sees AS61888 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 186.235.184.0/21 | RADB | No ROA |
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.