bgpreport

Network · data from 2026-11-12

AS274757 GRUPO TELECOM - CLM SERVIÇOS DE TELECOMUNICAÇÕES

Registry name: AS274757 - GRUPO TELECOM - JALLA, BR · PeeringDB

3IPv4 routes 100.0% RPKI valid · 33.3% with a route object
14IPv6 routes 100.0% RPKI valid · 7.1% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 15 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS274757, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS274757, 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.

192.6.194.0/24 Valid Nonecovered by 192.6.194.0/23 666 99% 67
192.6.195.0/24 Valid Nonecovered by 192.6.194.0/23 666 99% 67
2804:931c::/33 Valid Nonecovered by 2804:931c::/32 631 99% 67
2804:931c:100::/40 Valid Nonecovered by 2804:931c::/32 631 99% 69
2804:931c:8000::/33 Valid Nonecovered by 2804:931c::/32 631 99% 67
2804:931c::/34 Valid Nonecovered by 2804:931c::/32 626 98% 69
2804:931c:4000::/34 Valid Nonecovered by 2804:931c::/32 626 98% 69
2804:931c:8000::/34 Valid Nonecovered by 2804:931c::/32 626 98% 69
2804:931c:c000::/34 Valid Nonecovered by 2804:931c::/32 626 98% 69
2804:931c:100::/41 Valid Nonecovered by 2804:931c::/32 1 0%low visibility 1
2804:931c:100::/42 Valid Nonecovered by 2804:931c::/32 1 0%low visibility 1
2804:931c:140::/42 Valid Nonecovered by 2804:931c::/32 1 0%low visibility 1
2804:931c:180::/41 Valid Nonecovered by 2804:931c::/32 1 0%low visibility 1
2804:931c:180::/42 Valid Nonecovered by 2804:931c::/32 1 0%low visibility 1
2804:931c:1c0::/42 Valid Nonecovered by 2804:931c::/32 1 0%low visibility 1
2804:931c::/32 Valid Other IRR onlyRADB, TC 628 99% 67
64.204.60.0/24 Valid RIR databaseARIN, RADB 668 99% 67

AS-SET

PeeringDB's irr_as_set for AS274757: TC::AS274757:AS-GRUPOTELECOM. 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 (AS274757 isn't in the set, or no route object for AS274757 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 objectsAS274757 in itNot covered
TC::AS274757:AS-GRUPOTELECOM TC 2318 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 21 are in fix.csv.

  • Route object: none15
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none192.6.194.0/24No route object for it. A route object for 192.6.194.0/23 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.666 of 673
Route object: none192.6.195.0/24No route object for it. A route object for 192.6.194.0/23 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.666 of 673
Route object: none2804:931c::/33No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.631 of 636
Route object: none2804:931c:100::/40No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.631 of 636
Route object: none2804:931c:8000::/33No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.631 of 636
Route object: none2804:931c::/34No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.626 of 636
Route object: none2804:931c:4000::/34No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.626 of 636
Route object: none2804:931c:8000::/34No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.626 of 636
Route object: none2804:931c:c000::/34No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.626 of 636
Route object: none2804:931c:100::/41No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.1 of 636
Route object: none2804:931c:100::/42No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.1 of 636
Route object: none2804:931c:140::/42No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.1 of 636
Route object: none2804:931c:180::/41No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.1 of 636
Route object: none2804:931c:180::/42No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.1 of 636
Route object: none2804:931c:1c0::/42No route object for it. A route object for 2804:931c::/32 with origin AS274757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274757 in the RIR database for the space.1 of 636
Route object: RIR2804:931c::/32Route object only in RADB, TC. Add it in the RIR database for the space.628 of 636

Route objects not announced

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

38.226.114.0/23ALTDBNo ROA
38.226.114.0/24ALTDBNo ROA
38.226.115.0/24ALTDBNo ROA
192.6.94.0/23ALTDB, RADBNo ROA
192.6.194.0/23ARIN, RADBValid

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.