bgpreport

Network · data from 2026-11-12

AS274642 TELECOMUNICAÇOES BRASILIA LTDA

Registry name: AS274642 - TELECOMUNICACOES BRASILIA LTDA, BR · PeeringDB

4IPv4 routes 25.0% RPKI valid · 75.0% with a route object
7IPv6 routes 0.0% RPKI valid · 42.9% with a route object
0RPKI invalid 0 origin · 0 maxLength
10No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS274642, seen from no peer

Announced routes

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

177.131.97.0/24 No ROA None 672 100% 67
2804:74fc:8000::/34 No ROA Other origin only 636 100% 67
2804:9174:4100::/40 No ROA Nonecovered by 2804:9174::/32 635 100% 67
2804:9174:5b00::/40 No ROA Nonecovered by 2804:9174::/32 635 100% 67
2804:9174:4200::/40 No ROA Nonecovered by 2804:9174::/32 629 99% 67
177.223.158.0/24 No ROA Other IRR onlyALTDB 668 99% 66
38.20.6.0/24 No ROA Other IRR onlyRADB 667 99% 67
2804:9174:7900::/40 No ROA Other IRR onlyRADB 636 100% 67
2804:9174:7f00::/40 No ROA Other IRR onlyRADB 636 100% 67
2804:9174::/32 No ROA Other IRR onlyRADB, TC 353 56% 65
216.28.156.0/24 Valid RIR databaseARIN 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS274642: AS274642:AS-ALL. 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 (AS274642 isn't in the set, or no route object for AS274642 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 objectsAS274642 in itNot covered
AS274642:AS-ALL TC 127 Yes 2

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.

  • ROA: none10
  • Route object: none5
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none177.131.97.0/24No ROA covers it. Add a ROA for AS274642, maxLength 24.672 of 673
Route object: none177.131.97.0/24No route object for it. Add a route object with origin AS274642 in the RIR database for the space.672 of 673
ROA: none2804:74fc:8000::/34No ROA covers it. Add a ROA for AS274642, maxLength 34.636 of 636
Route object: none2804:74fc:8000::/34Route objects for it name AS271016. Add a route object with origin AS274642 in the RIR database for the space.636 of 636
ROA: none2804:9174:4100::/40No ROA covers it. Add a ROA for AS274642, maxLength 40.635 of 636
Route object: none2804:9174:4100::/40No route object for it. A route object for 2804:9174::/32 with origin AS274642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274642 in the RIR database for the space.635 of 636
ROA: none2804:9174:5b00::/40No ROA covers it. Add a ROA for AS274642, maxLength 40.635 of 636
Route object: none2804:9174:5b00::/40No route object for it. A route object for 2804:9174::/32 with origin AS274642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274642 in the RIR database for the space.635 of 636
ROA: none2804:9174:4200::/40No ROA covers it. Add a ROA for AS274642, maxLength 40.629 of 636
Route object: none2804:9174:4200::/40No route object for it. A route object for 2804:9174::/32 with origin AS274642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274642 in the RIR database for the space.629 of 636
ROA: none177.223.158.0/24No ROA covers it. Add a ROA for AS274642, maxLength 24.668 of 673
Route object: RIR177.223.158.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none38.20.6.0/24No ROA covers it. Add a ROA for AS274642, maxLength 24.667 of 673
Route object: RIR38.20.6.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:9174:7900::/40No ROA covers it. Add a ROA for AS274642, maxLength 40.636 of 636
Route object: RIR2804:9174:7900::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:9174:7f00::/40No ROA covers it. Add a ROA for AS274642, maxLength 40.636 of 636
Route object: RIR2804:9174:7f00::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:9174::/32No ROA covers it. Add a ROA for AS274642, maxLength 32.353 of 636
Route object: RIR2804:9174::/32Route object only in RADB, TC. Add it in the RIR database for the space.353 of 636

Route objects not announced

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

2804:9174::/48RADBNo 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.