bgpreport

Network · data from 2026-11-12

AS11271 Sencinet Latam Brasil

Registry name: AS11271 - SENCINET LATAM BRASIL LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11271, 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.218.185.0/24 No ROA Nonecovered by 200.218.128.0/18 669 99% 67
201.62.0.0/19 No ROA Other IRR onlyRADB 671 100% 67
200.218.146.0/24 No ROA Other IRR onlyRADB 670 100% 67
200.218.147.0/24 No ROA Other IRR onlyRADB 670 100% 67
200.218.188.0/24 No ROA Other IRR onlyRADB 670 100% 67
200.218.128.0/18 No ROA Other IRR onlyRADB 669 99% 67
200.219.160.0/19 No ROA Other IRR onlyRADB 669 99% 67
2800:23::/32 No ROA Other IRR onlyRADB 632 99% 67

AS-SET

AS11271's PeeringDB record names no AS-SET.

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 59 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced43
ChangePrefix or setDetailFull-table peers
ROA: none200.218.185.0/24No ROA covers it. Add a ROA for AS11271, maxLength 24.669 of 673
Route object: none200.218.185.0/24No route object for it. A route object for 200.218.128.0/18 with origin AS11271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11271 in the RIR database for the space.669 of 673
ROA: none201.62.0.0/19No ROA covers it. Add a ROA for AS11271, maxLength 19.671 of 673
Route object: RIR201.62.0.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.218.146.0/24No ROA covers it. Add a ROA for AS11271, maxLength 24.670 of 673
Route object: RIR200.218.146.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.218.147.0/24No ROA covers it. Add a ROA for AS11271, maxLength 24.670 of 673
Route object: RIR200.218.147.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.218.188.0/24No ROA covers it. Add a ROA for AS11271, maxLength 24.670 of 673
Route object: RIR200.218.188.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.218.128.0/18No ROA covers it. Add a ROA for AS11271, maxLength 18.669 of 673
Route object: RIR200.218.128.0/18Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none200.219.160.0/19No ROA covers it. Add a ROA for AS11271, maxLength 19.669 of 673
Route object: RIR200.219.160.0/19Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2800:23::/32No ROA covers it. Add a ROA for AS11271, maxLength 32.632 of 636
Route object: RIR2800:23::/32Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

200.218.129.0/24RADBNo ROA
200.218.131.0/24RADBNo ROA
200.218.133.0/24RADBNo ROA
200.218.141.0/24RADBNo ROA
200.218.142.0/24RADBNo ROA
200.218.152.0/24RADBNo ROA
200.218.153.0/24RADBNo ROA
200.218.154.0/24RADBNo ROA
200.218.167.0/24RADBNo ROA
200.218.171.0/24RADBNo ROA
200.218.172.0/24RADBNo ROA
200.218.182.0/24RADBNo ROA
200.218.183.0/24RADBNo ROA
200.218.184.0/24RADBNo ROA
200.218.186.0/24RADBNo ROA
200.219.161.0/24RADBNo ROA
200.219.162.0/24RADBNo ROA
200.219.164.0/24RADBNo ROA
200.219.165.0/24RADBNo ROA
200.219.173.0/24RADBNo ROA
200.219.180.0/24RADBNo ROA
201.62.14.0/24RADBNo ROA
201.62.28.0/24RADBNo ROA
2800:23:0:6::/64RADBNo ROA
2800:23:0:7::/64RADBNo ROA
2800:23:2:8::/64RADBNo ROA
2800:23:2:a::/64RADBNo ROA
2800:23:2:c::/64RADBNo ROA
2800:23:2:d::/64RADBNo ROA
2800:23:2:e::/64RADBNo ROA
2800:23:2:f::/64RADBNo ROA
2800:23:3:1::/64RADBNo ROA
2800:23:3:2::/64RADBNo ROA
2800:23:3:3::/64RADBNo ROA
2800:23:3:b::/64RADBNo ROA
2800:23:3:c::/64RADBNo ROA
2800:23:3:d::/64RADBNo ROA
2800:23:3:f::/64RADBNo ROA
2800:23:3:12::/64RADBNo ROA
2800:23:3:13::/64RADBNo ROA
2800:23:3:14::/64RADBNo ROA
2800:23:3:15::/64RADBNo ROA
2800:23:3:17::/64RADBNo 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.