bgpreport

Network · data from 2026-11-12

AS263303 PROVEDOR DE INTERNET SANTI LTDA - ME

Registry name: AS263303 - PROVEDOR DE INTERNET SANTI LTDA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263303, 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.190.248.0/22 No ROA Other IRR onlyTC 672 100% 66
2804:13f0::/32 No ROA Other IRR onlyRADB, TC 636 100% 67
177.190.248.0/21 No ROA Other IRR onlyRADB, TC 2 0%low visibility 2
177.190.252.0/22 No ROA Other IRR onlyTC 2 0%low visibility 2
177.190.248.0/23 No ROA Other IRR onlyTC 0 0%low visibility 1
177.190.250.0/23 No ROA Other IRR onlyTC 0 0%low visibility 1

AS-SET

AS263303'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 44 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none177.190.248.0/22No ROA covers it. Add a ROA for AS263303, maxLength 22.672 of 673
Route object: RIR177.190.248.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:13f0::/32No ROA covers it. Add a ROA for AS263303, maxLength 32.636 of 636
Route object: RIR2804:13f0::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none177.190.248.0/21No ROA covers it. Add a ROA for AS263303, maxLength 21.2 of 673
Route object: RIR177.190.248.0/21Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
ROA: none177.190.252.0/22No ROA covers it. Add a ROA for AS263303, maxLength 22.2 of 673
Route object: RIR177.190.252.0/22Route object only in TC. Add it in the RIR database for the space.2 of 673
ROA: none177.190.248.0/23No ROA covers it. Add a ROA for AS263303, maxLength 23.0 of 673
Route object: RIR177.190.248.0/23Route object only in TC. Add it in the RIR database for the space.0 of 673
ROA: none177.190.250.0/23No ROA covers it. Add a ROA for AS263303, maxLength 23.0 of 673
Route object: RIR177.190.250.0/23Route object only in TC. Add it in the RIR database for the space.0 of 673

Route objects not announced

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

177.190.248.0/24TCNo ROA
177.190.248.0/25TCNo ROA
177.190.248.128/25TCNo ROA
177.190.249.0/24TCNo ROA
177.190.249.0/25TCNo ROA
177.190.249.128/25TCNo ROA
177.190.250.0/24TCNo ROA
177.190.250.0/25TCNo ROA
177.190.250.128/25TCNo ROA
177.190.251.0/24TCNo ROA
177.190.251.0/25TCNo ROA
177.190.251.128/25TCNo ROA
177.190.252.0/23TCNo ROA
177.190.252.0/24TCNo ROA
177.190.252.0/25TCNo ROA
177.190.252.128/25TCNo ROA
177.190.253.0/24TCNo ROA
177.190.253.0/25TCNo ROA
177.190.253.128/25TCNo ROA
177.190.254.0/23TCNo ROA
177.190.254.0/24TCNo ROA
177.190.254.0/25TCNo ROA
177.190.254.128/25TCNo ROA
177.190.255.0/24TCNo ROA
177.190.255.0/25TCNo ROA
177.190.255.128/25TCNo ROA
2804:13f0::/33TCNo ROA
2804:13f0::/34TCNo ROA
2804:13f0:4000::/34TCNo ROA
2804:13f0:8000::/33TCNo ROA
2804:13f0:8000::/34TCNo ROA
2804:13f0: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.