bgpreport

Network · data from 2026-11-12

AS271247 RS Sul Telecomunicações

Registry name: AS271247 - RS Sul Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

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

200.106.215.0/24 No ROA Nonecovered by 200.106.214.0/23 666 99% 67
2804:833c::/32 No ROA Other origin only 435 68% 66
200.106.212.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
2804:7880::/32 No ROA Other IRR onlyRADB, TC 633 100% 67
200.106.212.0/23 No ROA Other IRR onlyRADB, TC 196 29% 54
200.106.214.0/23 No ROA Other IRR onlyRADB, TC 195 29% 54
2804:7880:100::/40 No ROA Other IRR onlyRADB, TC 6 1%low visibility 6
2804:7880:200::/40 No ROA Other IRR onlyRADB, TC 6 1%low visibility 6
2804:7880:1000::/40 No ROA Other IRR onlyRADB, TC 6 1%low visibility 6

AS-SET

PeeringDB's irr_as_set for AS271247: AS271247:AS-RSSUL-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 (AS271247 isn't in the set, or no route object for AS271247 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 objectsAS271247 in itNot covered
AS271247:AS-RSSUL-ALL TC 8385 Yes 1

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: none9
  • Route object: none2
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none200.106.215.0/24No ROA covers it. Add a ROA for AS271247, maxLength 24.666 of 673
Route object: none200.106.215.0/24No route object for it. A route object for 200.106.214.0/23 with origin AS271247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271247 in the RIR database for the space.666 of 673
ROA: none2804:833c::/32No ROA covers it. Add a ROA for AS271247, maxLength 32.435 of 636
Route object: none2804:833c::/32Route objects for it name AS272185. Add a route object with origin AS271247 in the RIR database for the space.435 of 636
ROA: none200.106.212.0/22No ROA covers it. Add a ROA for AS271247, maxLength 22.672 of 673
Route object: RIR200.106.212.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:7880::/32No ROA covers it. Add a ROA for AS271247, maxLength 32.633 of 636
Route object: RIR2804:7880::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
ROA: none200.106.212.0/23No ROA covers it. Add a ROA for AS271247, maxLength 23.196 of 673
Route object: RIR200.106.212.0/23Route object only in RADB, TC. Add it in the RIR database for the space.196 of 673
ROA: none200.106.214.0/23No ROA covers it. Add a ROA for AS271247, maxLength 23.195 of 673
Route object: RIR200.106.214.0/23Route object only in RADB, TC. Add it in the RIR database for the space.195 of 673
ROA: none2804:7880:100::/40No ROA covers it. Add a ROA for AS271247, maxLength 40.6 of 636
Route object: RIR2804:7880:100::/40Route object only in RADB, TC. Add it in the RIR database for the space.6 of 636
ROA: none2804:7880:200::/40No ROA covers it. Add a ROA for AS271247, maxLength 40.6 of 636
Route object: RIR2804:7880:200::/40Route object only in RADB, TC. Add it in the RIR database for the space.6 of 636
ROA: none2804:7880:1000::/40No ROA covers it. Add a ROA for AS271247, maxLength 40.6 of 636
Route object: RIR2804:7880:1000::/40Route object only in RADB, TC. Add it in the RIR database for the space.6 of 636

Route objects not announced

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

200.106.212.0/24RADB, TCNo ROA
200.106.213.0/24TCNo ROA
200.106.214.0/24RADB, 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.