bgpreport

Network · data from 2026-11-12

AS265181 S1 TELECOM

Registry name: AS265181 - S1 Telecomunicacoes e Sistemas de Informacao LTDA, BR · PeeringDB

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

Announced routes

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

170.233.36.0/23 No ROA Nonecovered by 170.233.36.0/22 65 10%low visibility 21
170.233.38.0/23 No ROA Nonecovered by 170.233.36.0/22 65 10%low visibility 21
167.249.134.0/24 No ROA Nonecovered by 167.249.132.0/22 5 1%low visibility 4
170.233.36.0/24 No ROA Nonecovered by 170.233.36.0/22 5 1%low visibility 4
170.233.37.0/24 No ROA Nonecovered by 170.233.36.0/22 5 1%low visibility 4
167.249.132.0/22 No ROA Other IRR onlyTC 663 99% 66
170.233.36.0/22 No ROA Other IRR onlyRADB, TC 663 99% 66
167.249.135.0/24 No ROA Other IRR onlyRADB 5 1%low visibility 4
170.233.38.0/24 No ROA Other IRR onlyRADB 5 1%low visibility 4
170.233.39.0/24 No ROA Other IRR onlyRADB 5 1%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS265181: AS-S1TELECOM. 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 (AS265181 isn't in the set, or no route object for AS265181 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 objectsAS265181 in itNot covered
AS-S1TELECOM TC 6157 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.

  • ROA: none10
  • Route object: none5
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none170.233.36.0/23No ROA covers it. Add a ROA for AS265181, maxLength 23.65 of 673
Route object: none170.233.36.0/23No route object for it. A route object for 170.233.36.0/22 with origin AS265181 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265181 in the RIR database for the space.65 of 673
ROA: none170.233.38.0/23No ROA covers it. Add a ROA for AS265181, maxLength 23.65 of 673
Route object: none170.233.38.0/23No route object for it. A route object for 170.233.36.0/22 with origin AS265181 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265181 in the RIR database for the space.65 of 673
ROA: none167.249.134.0/24No ROA covers it. Add a ROA for AS265181, maxLength 24.5 of 673
Route object: none167.249.134.0/24No route object for it. A route object for 167.249.132.0/22 with origin AS265181 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265181 in the RIR database for the space.5 of 673
ROA: none170.233.36.0/24No ROA covers it. Add a ROA for AS265181, maxLength 24.5 of 673
Route object: none170.233.36.0/24No route object for it. A route object for 170.233.36.0/22 with origin AS265181 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265181 in the RIR database for the space.5 of 673
ROA: none170.233.37.0/24No ROA covers it. Add a ROA for AS265181, maxLength 24.5 of 673
Route object: none170.233.37.0/24No route object for it. A route object for 170.233.36.0/22 with origin AS265181 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265181 in the RIR database for the space.5 of 673
ROA: none167.249.132.0/22No ROA covers it. Add a ROA for AS265181, maxLength 22.663 of 673
Route object: RIR167.249.132.0/22Route object only in TC. Add it in the RIR database for the space.663 of 673
ROA: none170.233.36.0/22No ROA covers it. Add a ROA for AS265181, maxLength 22.663 of 673
Route object: RIR170.233.36.0/22Route object only in RADB, TC. Add it in the RIR database for the space.663 of 673
ROA: none167.249.135.0/24No ROA covers it. Add a ROA for AS265181, maxLength 24.5 of 673
Route object: RIR167.249.135.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
ROA: none170.233.38.0/24No ROA covers it. Add a ROA for AS265181, maxLength 24.5 of 673
Route object: RIR170.233.38.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
ROA: none170.233.39.0/24No ROA covers it. Add a ROA for AS265181, maxLength 24.5 of 673
Route object: RIR170.233.39.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673

Route objects not announced

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

2804:2bdc::/32RADB, TCNo 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.