bgpreport

Network · data from 2026-11-12

AS272732 ONLY SERVICOS DE TELECOMUNICACOES LTDA

Registry name: AS272732 - ONLY SERVICOS DE TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272732, 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:87cc:1000::/40 No ROA Other IRR onlyRADB 634 100% 67
2804:87cc:1100::/40 No ROA Other IRR onlyRADB 634 100% 67
2804:87cc:1200::/40 No ROA Other IRR onlyRADB 634 100% 67
2804:87cc:1300::/40 No ROA Other IRR onlyRADB 634 100% 67
38.224.59.0/24 Valid RIR databaseARIN 671 100% 66
38.224.58.0/24 Valid RIR databaseARIN 669 99% 66
38.226.196.0/24 Valid RIR databaseARIN 669 99% 66

AS-SET

PeeringDB's irr_as_set for AS272732: AS272732: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 (AS272732 isn't in the set, or no route object for AS272732 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 objectsAS272732 in itNot covered
AS272732:AS-ANNOUNCEMENTS TC 2221 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 17 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none2804:87cc:1000::/40No ROA covers it. Add a ROA for AS272732, maxLength 40.634 of 636
Route object: RIR2804:87cc:1000::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:87cc:1100::/40No ROA covers it. Add a ROA for AS272732, maxLength 40.634 of 636
Route object: RIR2804:87cc:1100::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:87cc:1200::/40No ROA covers it. Add a ROA for AS272732, maxLength 40.634 of 636
Route object: RIR2804:87cc:1200::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:87cc:1300::/40No ROA covers it. Add a ROA for AS272732, maxLength 40.634 of 636
Route object: RIR2804:87cc:1300::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

38.224.58.0/23ARINValid
45.190.97.0/24RADBNo ROA
2804:87cc::/32RADB, TCNo ROA
2804:87cc::/33TCNo ROA
2804:87cc::/34TCNo ROA
2804:87cc:4000::/34TCNo ROA
2804:87cc:8000::/33TCNo ROA
2804:87cc:8000::/34TCNo ROA
2804:87cc:c000::/34TCNo 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.