bgpreport

Network · data from 2026-11-12

AS37183 Utande Internet Services

Registry name: Utande Internet Services (Pvt) Ltd - Utande Internet Services (Pvt) Ltd, ZW · PeeringDB

81IPv4 routes 82.7% RPKI valid · 77.8% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
2RPKI invalid 0 origin · 2 maxLength
13No ROA 18 with no route object for this origin
22Low visibility seen by under 10% of full-table peers
34Route objects not announced registered with origin AS37183, seen from no peer

Announced routes

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

196.29.32.0/22 Invalid: maxLength Nonecovered by 196.29.32.0/21 6 1%low visibility 4
196.29.36.0/22 Invalid: maxLength Nonecovered by 196.29.32.0/21 6 1%low visibility 4
196.2.67.0/24 No ROA Nonecovered by 196.2.64.0/20 673 100% 67
196.2.76.0/24 No ROA Nonecovered by 196.2.64.0/20 673 100% 67
196.2.64.0/24 No ROA Nonecovered by 196.2.64.0/20 672 100% 67
196.2.66.0/24 No ROA Nonecovered by 196.2.64.0/20 672 100% 67
196.2.69.0/24 No ROA Nonecovered by 196.2.64.0/20 672 100% 67
196.2.72.0/24 No ROA Nonecovered by 196.2.64.0/20 672 100% 67
196.2.73.0/24 No ROA Nonecovered by 196.2.64.0/20 672 100% 67
102.165.112.0/24 No ROA Other origin only 670 100% 69
196.2.64.0/21 No ROA Nonecovered by 196.2.64.0/20 39 6%low visibility 16
196.2.72.0/21 No ROA Nonecovered by 196.2.64.0/20 39 6%low visibility 16
196.2.75.0/24 No ROA Nonecovered by 196.2.64.0/20 39 6%low visibility 16
196.2.64.0/20 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67
2001:43f0::/32 No ROA Other IRR onlyRIPE-NONAUTH 636 100% 67
196.43.112.0/22 Valid Nonecovered by 196.43.112.0/21 673 100% 67
41.85.195.0/24 Valid Nonecovered by 41.85.194.0/23 672 100% 67
41.85.196.0/23 Valid Nonecovered by 41.85.192.0/21 39 6%low visibility 16
41.85.199.0/24 Valid Nonecovered by 41.85.198.0/23 39 6%low visibility 16
196.43.112.0/20 Valid Nonecovered by 196.43.96.0/19 39 6%low visibility 16
41.85.192.0/23 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
41.85.193.0/24 Valid RIR databaseAFRINIC 672 100% 67
41.85.194.0/23 Valid RIR databaseAFRINIC 672 100% 67
196.29.32.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
196.29.33.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
196.29.34.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
196.29.35.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
196.29.36.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
196.29.37.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
196.29.38.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
196.29.39.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
196.43.96.0/19 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
196.43.96.0/24 Valid RIR databaseAFRINIC 672 100% 67
196.43.97.0/24 Valid RIR databaseAFRINIC 672 100% 67
196.43.98.0/24 Valid RIR databaseAFRINIC 672 100% 67
196.43.100.0/24 Valid RIR databaseAFRINIC 672 100% 67
196.43.105.0/24 Valid RIR databaseAFRINIC 672 100% 67
196.43.108.0/24 Valid RIR databaseAFRINIC 672 100% 67
196.43.111.0/24 Valid RIR databaseAFRINIC 672 100% 67
196.43.112.0/21 Valid RIR databaseAFRINIC 672 100% 67
196.43.115.0/24 Valid RIR databaseAFRINIC 672 100% 67
41.85.192.0/24 Valid RIR databaseAFRINIC 671 100% 67
41.85.214.0/24 Valid RIR databaseAFRINIC 671 100% 68
196.43.116.0/24 Valid RIR databaseAFRINIC 671 100% 68
196.43.118.0/24 Valid RIR databaseAFRINIC 671 100% 68
196.43.119.0/24 Valid RIR databaseAFRINIC 671 100% 68
196.43.124.0/22 Valid RIR databaseAFRINIC 671 100% 68
196.44.178.0/24 Valid RIR databaseAFRINIC 671 100% 68
41.85.194.0/24 Valid RIR databaseAFRINIC 670 100% 68
41.85.210.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.29.32.0/21 Valid RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 68
196.43.96.0/20 Valid RIR databaseAFRINIC 670 100% 68
196.43.99.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.101.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.102.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.103.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 68
196.43.104.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.106.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.107.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.109.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.110.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.112.0/23 Valid RIR databaseAFRINIC 670 100% 68
196.43.112.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.113.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.114.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.116.0/23 Valid RIR databaseAFRINIC 670 100% 68
196.43.117.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.125.0/24 Valid RIR databaseAFRINIC 670 100% 68
196.43.114.0/23 Valid RIR databaseAFRINIC 41 6%low visibility 17
41.85.196.0/24 Valid RIR databaseAFRINIC 39 6%low visibility 16
41.85.198.0/23 Valid RIR databaseAFRINIC 39 6%low visibility 16
41.85.198.0/24 Valid RIR databaseAFRINIC 39 6%low visibility 16
196.29.32.0/23 Valid RIR databaseAFRINIC, RIPE-NONAUTH 39 6%low visibility 16
196.29.34.0/23 Valid RIR databaseAFRINIC, RIPE-NONAUTH 39 6%low visibility 16
196.29.36.0/23 Valid RIR databaseAFRINIC, RIPE-NONAUTH 39 6%low visibility 16
196.29.38.0/23 Valid RIR databaseAFRINIC, RIPE-NONAUTH 39 6%low visibility 16
196.43.96.0/23 Valid RIR databaseAFRINIC 39 6%low visibility 16
196.43.104.0/23 Valid RIR databaseAFRINIC 39 6%low visibility 16
196.43.106.0/23 Valid RIR databaseAFRINIC 39 6%low visibility 16
196.43.124.0/24 Valid RIR databaseAFRINIC 39 6%low visibility 16
196.43.126.0/24 Valid RIR databaseAFRINIC 39 6%low visibility 16
196.43.127.0/24 Valid RIR databaseAFRINIC 39 6%low visibility 16

AS-SET

PeeringDB's irr_as_set for AS37183: AS-UTANDE. 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 (AS37183 isn't in the set, or no route object for AS37183 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 objectsAS37183 in itNot covered
AS-UTANDE In no IRR database read today.

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

  • ROA: maxLength2
  • ROA: none13
  • Route object: none18
  • Route object: RIR2
  • AS-SET: not found1
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
ROA: maxLength196.29.32.0/22ROA 196.29.32.0/21 AS37183 has maxLength 21; the route is a /22. Raise the maxLength, or add a ROA for 196.29.32.0/22.6 of 673
Route object: none196.29.32.0/22No route object for it. A route object for 196.29.32.0/21 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.6 of 673
ROA: maxLength196.29.36.0/22ROA 196.29.32.0/21 AS37183 has maxLength 21; the route is a /22. Raise the maxLength, or add a ROA for 196.29.36.0/22.6 of 673
Route object: none196.29.36.0/22No route object for it. A route object for 196.29.32.0/21 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.6 of 673
ROA: none196.2.67.0/24No ROA covers it. Add a ROA for AS37183, maxLength 24.673 of 673
Route object: none196.2.67.0/24No route object for it. A route object for 196.2.64.0/20 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.673 of 673
ROA: none196.2.76.0/24No ROA covers it. Add a ROA for AS37183, maxLength 24.673 of 673
Route object: none196.2.76.0/24No route object for it. A route object for 196.2.64.0/20 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.673 of 673
ROA: none196.2.64.0/24No ROA covers it. Add a ROA for AS37183, maxLength 24.672 of 673
Route object: none196.2.64.0/24No route object for it. A route object for 196.2.64.0/20 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.672 of 673
ROA: none196.2.66.0/24No ROA covers it. Add a ROA for AS37183, maxLength 24.672 of 673
Route object: none196.2.66.0/24No route object for it. A route object for 196.2.64.0/20 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.672 of 673
ROA: none196.2.69.0/24No ROA covers it. Add a ROA for AS37183, maxLength 24.672 of 673
Route object: none196.2.69.0/24No route object for it. A route object for 196.2.64.0/20 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.672 of 673
ROA: none196.2.72.0/24No ROA covers it. Add a ROA for AS37183, maxLength 24.672 of 673
Route object: none196.2.72.0/24No route object for it. A route object for 196.2.64.0/20 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.672 of 673
ROA: none196.2.73.0/24No ROA covers it. Add a ROA for AS37183, maxLength 24.672 of 673
Route object: none196.2.73.0/24No route object for it. A route object for 196.2.64.0/20 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.672 of 673
ROA: none102.165.112.0/24No ROA covers it. Add a ROA for AS37183, maxLength 24.670 of 673
Route object: none102.165.112.0/24Route objects for it name AS328291. Add a route object with origin AS37183 in the RIR database for the space.670 of 673
ROA: none196.2.64.0/21No ROA covers it. Add a ROA for AS37183, maxLength 21.39 of 673
Route object: none196.2.64.0/21No route object for it. A route object for 196.2.64.0/20 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.39 of 673
ROA: none196.2.72.0/21No ROA covers it. Add a ROA for AS37183, maxLength 21.39 of 673
Route object: none196.2.72.0/21No route object for it. A route object for 196.2.64.0/20 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.39 of 673
ROA: none196.2.75.0/24No ROA covers it. Add a ROA for AS37183, maxLength 24.39 of 673
Route object: none196.2.75.0/24No route object for it. A route object for 196.2.64.0/20 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.39 of 673
ROA: none196.2.64.0/20No ROA covers it. Add a ROA for AS37183, maxLength 20.672 of 673
Route object: RIR196.2.64.0/20Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none2001:43f0::/32No ROA covers it. Add a ROA for AS37183, maxLength 32.636 of 636
Route object: RIR2001:43f0::/32Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.636 of 636
Route object: none196.43.112.0/22No route object for it. A route object for 196.43.112.0/21 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.673 of 673
Route object: none41.85.195.0/24No route object for it. A route object for 41.85.194.0/23 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.672 of 673
Route object: none41.85.196.0/23No route object for it. A route object for 41.85.192.0/21 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.39 of 673
Route object: none41.85.199.0/24No route object for it. A route object for 41.85.198.0/23 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.39 of 673
Route object: none196.43.112.0/20No route object for it. A route object for 196.43.96.0/19 with origin AS37183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37183 in the RIR database for the space.39 of 673
AS-SET: not foundAS-UTANDEPeeringDB names AS-UTANDE; no IRR database read has it.

Route objects not announced

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

41.85.192.0/19AFRINICNo ROA
41.85.192.0/21AFRINICValid
41.85.210.0/23AFRINICValid
41.85.211.0/24AFRINICValid
41.85.212.0/23AFRINIC, RIPE-NONAUTHValid
41.85.212.0/24AFRINICValid
41.85.213.0/24AFRINICValid
41.85.214.0/23AFRINICValid
41.85.215.0/24AFRINICValid
41.85.216.0/22AFRINICInvalid: maxLength
41.85.216.0/23AFRINICValid
41.85.216.0/24AFRINICValid
41.85.217.0/24AFRINICValid
41.85.218.0/23AFRINICValid
41.85.218.0/24AFRINICValid
41.85.219.0/24AFRINICValid
41.85.220.0/23AFRINICValid
41.85.220.0/24AFRINICValid
41.85.221.0/24AFRINICValid
41.85.222.0/23AFRINICValid
41.85.222.0/24AFRINICValid
41.85.223.0/24AFRINICValid
41.190.38.0/24AFRINICNo ROA
196.29.28.0/24RIPE-NONAUTHNo ROA
196.43.98.0/23AFRINICValid
196.43.100.0/23AFRINICValid
196.43.102.0/23AFRINICValid
196.43.108.0/23AFRINICValid
196.43.110.0/23AFRINICValid
196.43.118.0/23AFRINICValid
196.43.124.0/23AFRINICValid
196.43.126.0/23AFRINICValid
196.44.186.0/24AFRINICNo ROA
2001:470:18a::/48ARINValid

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.