bgpreport

Network · data from 2026-11-12

AS263320 AS263320 - Sansara Telecom

Registry name: AS263320 - Sansara Telecom, BR · not in PeeringDB

19IPv4 routes 84.2% RPKI valid · 89.5% with a route object
21IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS263320, seen from no peer

Announced routes

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

187.45.133.0/24 No ROA Other origin only 667 99% 67
45.171.1.0/24 No ROA None 666 99% 67
45.171.3.0/24 No ROA Other IRR onlyRADB 667 99% 67
191.7.152.0/24 Valid Other IRR onlyRADB, TC 668 99% 66
191.7.156.0/24 Valid Other IRR onlyRADB, TC 668 99% 66
191.7.146.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
191.7.147.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
191.7.149.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
191.7.150.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
191.7.154.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
191.7.158.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
191.7.159.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
191.7.144.0/24 Valid Other IRR onlyRADB, TC 666 99% 67
191.7.148.0/24 Valid Other IRR onlyRADB, TC 666 99% 67
191.7.153.0/24 Valid Other IRR onlyRADB, TC 666 99% 66
191.7.145.0/24 Valid Other IRR onlyRADB, TC 665 99% 66
191.7.157.0/24 Valid Other IRR onlyRADB, TC 665 99% 67
191.7.151.0/24 Valid Other IRR onlyRADB, TC 663 99% 67
191.7.155.0/24 Valid Other IRR onlyRADB, TC 663 99% 67
2804:143c:ff50::/44 Valid Other IRR onlyRADB 632 99% 67
2804:143c:ff50::/46 Valid Other IRR onlyRADB 632 99% 67
2804:143c:ff54::/46 Valid Other IRR onlyRADB 632 99% 67
2804:143c::/32 Valid Other IRR onlyRADB, TC 631 99% 69
2804:143c::/33 Valid Other IRR onlyTC 631 99% 69
2804:143c:8000::/33 Valid Other IRR onlyTC 631 99% 69
2804:143c:ff00::/44 Valid Other IRR onlyRADB 631 99% 67
2804:143c:ff40::/44 Valid Other IRR onlyRADB 631 99% 69
2804:143c:ff40::/45 Valid Other IRR onlyRADB 631 99% 69
2804:143c:ff40::/46 Valid Other IRR onlyRADB 631 99% 69
2804:143c:ff44::/46 Valid Other IRR onlyRADB 631 99% 69
2804:143c:ff48::/45 Valid Other IRR onlyRADB 631 99% 69
2804:143c:ff48::/46 Valid Other IRR onlyRADB 631 99% 69
2804:143c:ff4c::/46 Valid Other IRR onlyRADB 631 99% 69
2804:143c:ff10::/44 Valid Other IRR onlyRADB 630 99% 67
2804:143c:ff30::/44 Valid Other IRR onlyRADB 630 99% 67
2804:143c:ffb0::/44 Valid Other IRR onlyRADB 630 99% 67
2804:143c:ffd0::/44 Valid Other IRR onlyALTDB, RADB 628 99% 67
2804:143c:ffd0::/45 Valid Other IRR onlyRADB 628 99% 67
2804:143c:ffd8::/45 Valid Other IRR onlyRADB 628 99% 67
2804:143c:ff60::/44 Valid Other IRR onlyRADB 627 99% 67

AS-SET

AS263320 isn't in PeeringDB, where networks name their 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 52 are in fix.csv.

  • ROA: none3
  • Route object: none2
  • Route object: RIR38
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none187.45.133.0/24No ROA covers it. Add a ROA for AS263320, maxLength 24.667 of 673
Route object: none187.45.133.0/24Route objects for it name AS28136. Add a route object with origin AS263320 in the RIR database for the space.667 of 673
ROA: none45.171.1.0/24No ROA covers it. Add a ROA for AS263320, maxLength 24.666 of 673
Route object: none45.171.1.0/24No route object for it. Add a route object with origin AS263320 in the RIR database for the space.666 of 673
ROA: none45.171.3.0/24No ROA covers it. Add a ROA for AS263320, maxLength 24.667 of 673
Route object: RIR45.171.3.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR191.7.152.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR191.7.156.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR191.7.146.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR191.7.147.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR191.7.149.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR191.7.150.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR191.7.154.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR191.7.158.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR191.7.159.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR191.7.144.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR191.7.148.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR191.7.153.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR191.7.145.0/24Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR191.7.157.0/24Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR191.7.151.0/24Route object only in RADB, TC. Add it in the RIR database for the space.663 of 673
Route object: RIR191.7.155.0/24Route object only in RADB, TC. Add it in the RIR database for the space.663 of 673
Route object: RIR2804:143c:ff50::/44Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:143c:ff50::/46Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:143c:ff54::/46Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:143c::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:143c::/33Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:143c:8000::/33Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:143c:ff00::/44Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:143c:ff40::/44Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:143c:ff40::/45Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:143c:ff40::/46Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:143c:ff44::/46Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:143c:ff48::/45Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:143c:ff48::/46Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:143c:ff4c::/46Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:143c:ff10::/44Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:143c:ff30::/44Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:143c:ffb0::/44Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:143c:ffd0::/44Route object only in ALTDB, RADB. Add it in the RIR database for the space.628 of 636
Route object: RIR2804:143c:ffd0::/45Route object only in RADB. Add it in the RIR database for the space.628 of 636
Route object: RIR2804:143c:ffd8::/45Route object only in RADB. Add it in the RIR database for the space.628 of 636
Route object: RIR2804:143c:ff60::/44Route object only in RADB. Add it in the RIR database for the space.627 of 636

Route objects not announced

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

191.7.144.0/20RADB, TCValid
191.7.152.0/23RADBValid
191.7.154.0/23RADBValid
2607:1640:1035::/48RADBNo ROA
2804:143c:ff20::/44RADBValid
2804:143c:ff70::/44RADBValid
2804:143c:ff90::/44RADBValid
2804:143c:ffa0::/44RADBValid
2804:143c:ffc0::/44TCValid

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.