bgpreport

Network · data from 2026-11-12

AS53070 T-Systems Brazil

Registry name: AS53070 - T-Systems do Brasil Ltda., BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53070, 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.36.224.0/20 No ROA Other IRR onlyNTTCOM, RADB, TC 672 100% 67
177.36.226.0/24 No ROA Other IRR onlyNTTCOM, TC 672 100% 66
187.86.208.0/20 No ROA Other IRR onlyNTTCOM, RADB, TC 672 100% 67
187.86.216.0/23 No ROA Other IRR onlyNTTCOM, TC 672 100% 67
177.36.224.0/22 No ROA Other IRR onlyNTTCOM, TC 671 100% 67
177.36.228.0/22 No ROA Other IRR onlyNTTCOM, TC 671 100% 67
177.36.236.0/22 No ROA Other IRR onlyNTTCOM, TC 671 100% 67
177.36.236.0/23 No ROA Other IRR onlyNTTCOM 671 100% 67
187.86.208.0/22 No ROA Other IRR onlyNTTCOM, TC 671 100% 67
187.86.216.0/22 No ROA Other IRR onlyNTTCOM, TC 671 100% 67
187.86.220.0/22 No ROA Other IRR onlyNTTCOM, TC 671 100% 67
177.36.232.0/22 No ROA Other IRR onlyNTTCOM, TC 670 100% 67
187.86.212.0/22 No ROA Other IRR onlyNTTCOM, TC 670 100% 67
187.86.218.0/23 No ROA Other IRR onlyNTTCOM, TC 670 100% 67
2804:68::/33 No ROA Other IRR onlyNTTCOM, RADB, TC 636 100% 67
2804:68:8000::/33 No ROA Other IRR onlyNTTCOM, RADB, TC 636 100% 67
2804:68::/32 No ROA Other IRR onlyNTTCOM, TC 633 100% 67

AS-SET

AS53070'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 97 are in fix.csv.

  • ROA: none17
  • Route object: RIR17
  • Route object: not announced63
ChangePrefix or setDetailFull-table peers
ROA: none177.36.224.0/20No ROA covers it. Add a ROA for AS53070, maxLength 20.672 of 673
Route object: RIR177.36.224.0/20Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none177.36.226.0/24No ROA covers it. Add a ROA for AS53070, maxLength 24.672 of 673
Route object: RIR177.36.226.0/24Route object only in NTTCOM, TC. Add it in the RIR database for the space.672 of 673
ROA: none187.86.208.0/20No ROA covers it. Add a ROA for AS53070, maxLength 20.672 of 673
Route object: RIR187.86.208.0/20Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none187.86.216.0/23No ROA covers it. Add a ROA for AS53070, maxLength 23.672 of 673
Route object: RIR187.86.216.0/23Route object only in NTTCOM, TC. Add it in the RIR database for the space.672 of 673
ROA: none177.36.224.0/22No ROA covers it. Add a ROA for AS53070, maxLength 22.671 of 673
Route object: RIR177.36.224.0/22Route object only in NTTCOM, TC. Add it in the RIR database for the space.671 of 673
ROA: none177.36.228.0/22No ROA covers it. Add a ROA for AS53070, maxLength 22.671 of 673
Route object: RIR177.36.228.0/22Route object only in NTTCOM, TC. Add it in the RIR database for the space.671 of 673
ROA: none177.36.236.0/22No ROA covers it. Add a ROA for AS53070, maxLength 22.671 of 673
Route object: RIR177.36.236.0/22Route object only in NTTCOM, TC. Add it in the RIR database for the space.671 of 673
ROA: none177.36.236.0/23No ROA covers it. Add a ROA for AS53070, maxLength 23.671 of 673
Route object: RIR177.36.236.0/23Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none187.86.208.0/22No ROA covers it. Add a ROA for AS53070, maxLength 22.671 of 673
Route object: RIR187.86.208.0/22Route object only in NTTCOM, TC. Add it in the RIR database for the space.671 of 673
ROA: none187.86.216.0/22No ROA covers it. Add a ROA for AS53070, maxLength 22.671 of 673
Route object: RIR187.86.216.0/22Route object only in NTTCOM, TC. Add it in the RIR database for the space.671 of 673
ROA: none187.86.220.0/22No ROA covers it. Add a ROA for AS53070, maxLength 22.671 of 673
Route object: RIR187.86.220.0/22Route object only in NTTCOM, TC. Add it in the RIR database for the space.671 of 673
ROA: none177.36.232.0/22No ROA covers it. Add a ROA for AS53070, maxLength 22.670 of 673
Route object: RIR177.36.232.0/22Route object only in NTTCOM, TC. Add it in the RIR database for the space.670 of 673
ROA: none187.86.212.0/22No ROA covers it. Add a ROA for AS53070, maxLength 22.670 of 673
Route object: RIR187.86.212.0/22Route object only in NTTCOM, TC. Add it in the RIR database for the space.670 of 673
ROA: none187.86.218.0/23No ROA covers it. Add a ROA for AS53070, maxLength 23.670 of 673
Route object: RIR187.86.218.0/23Route object only in NTTCOM, TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:68::/33No ROA covers it. Add a ROA for AS53070, maxLength 33.636 of 636
Route object: RIR2804:68::/33Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:68:8000::/33No ROA covers it. Add a ROA for AS53070, maxLength 33.636 of 636
Route object: RIR2804:68:8000::/33Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:68::/32No ROA covers it. Add a ROA for AS53070, maxLength 32.633 of 636
Route object: RIR2804:68::/32Route object only in NTTCOM, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

177.36.224.0/21NTTCOM, TCNo ROA
177.36.224.0/23NTTCOMNo ROA
177.36.224.0/24NTTCOM, TCNo ROA
177.36.225.0/24NTTCOM, TCNo ROA
177.36.226.0/23NTTCOMNo ROA
177.36.227.0/24NTTCOM, TCNo ROA
177.36.228.0/23NTTCOMNo ROA
177.36.228.0/24NTTCOM, TCNo ROA
177.36.229.0/24NTTCOM, TCNo ROA
177.36.230.0/23NTTCOMNo ROA
177.36.230.0/24NTTCOM, TCNo ROA
177.36.231.0/24NTTCOM, TCNo ROA
177.36.232.0/21NTTCOM, TCNo ROA
177.36.232.0/23NTTCOMNo ROA
177.36.232.0/24NTTCOM, TCNo ROA
177.36.233.0/24NTTCOM, TCNo ROA
177.36.234.0/23NTTCOMNo ROA
177.36.234.0/24NTTCOM, TCNo ROA
177.36.235.0/24NTTCOM, TCNo ROA
177.36.236.0/24NTTCOM, TCNo ROA
177.36.237.0/24NTTCOM, TCNo ROA
177.36.238.0/23NTTCOM, TCNo ROA
177.36.238.0/24NTTCOM, TCNo ROA
177.36.239.0/24NTTCOM, TCNo ROA
186.208.88.0/21NTTCOM, RADBNo ROA
186.208.92.0/22NTTCOMNo ROA
186.208.92.0/24NTTCOMNo ROA
186.208.93.0/24NTTCOMNo ROA
186.208.94.0/23NTTCOMNo ROA
186.208.94.0/24NTTCOMNo ROA
186.208.95.0/24NTTCOMNo ROA
187.86.208.0/21NTTCOM, TCNo ROA
187.86.208.0/23NTTCOM, TCNo ROA
187.86.208.0/24NTTCOM, TCNo ROA
187.86.209.0/24NTTCOM, TCNo ROA
187.86.210.0/23NTTCOM, TCNo ROA
187.86.210.0/24NTTCOM, RADB, TCNo ROA
187.86.211.0/24NTTCOM, TCNo ROA
187.86.212.0/23NTTCOM, TCNo ROA
187.86.212.0/24NTTCOM, TCNo ROA
187.86.213.0/24NTTCOM, TCNo ROA
187.86.214.0/23NTTCOM, TCNo ROA
187.86.214.0/24NTTCOM, TCNo ROA
187.86.215.0/24NTTCOM, TCNo ROA
187.86.216.0/21NTTCOM, TCNo ROA
187.86.216.0/24NTTCOM, TCNo ROA
187.86.217.0/24NTTCOM, TCNo ROA
187.86.218.0/24NTTCOM, TCNo ROA
187.86.219.0/24NTTCOM, TCNo ROA
187.86.220.0/23NTTCOM, TCNo ROA
187.86.220.0/24NTTCOM, TCNo ROA
187.86.221.0/24NTTCOM, TCNo ROA
187.86.222.0/23NTTCOM, TCNo ROA
187.86.222.0/24NTTCOM, TCNo ROA
187.86.223.0/24NTTCOM, TCNo ROA
2804:68::/34NTTCOM, RADB, TCNo ROA
2804:68::/35NTTCOM, TCNo ROA
2804:68:2000::/35NTTCOM, TCNo ROA
2804:68:4000::/34RADB, TCNo ROA
2804:68:4000::/35NTTCOM, TCNo ROA
2804:68:6000::/35NTTCOM, TCNo ROA
2804:68:8000::/34RADBNo ROA
2804:68:c000::/34RADBNo 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.