bgpreport

Network · data from 2026-11-12

AS36731 Zip Telecom

Registry name: SERVER-CLOUD-CANADA - Server Cloud Canada Inc, CA · PeeringDB

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

Announced routes

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

173.46.20.0/24 No ROA Other IRR onlyALTDB 668 99% 67
173.46.22.0/24 No ROA Other IRR onlyALTDB 668 99% 67
173.46.23.0/24 No ROA Other IRR onlyALTDB 668 99% 67
173.46.24.0/23 No ROA Other IRR onlyALTDB 668 99% 67
173.46.31.0/24 No ROA Other IRR onlyALTDB 668 99% 67
2602:ffc1::/32 Valid None 632 99% 68
67.22.120.0/21 Valid RIR databaseARIN 670 100% 67
67.22.120.0/24 Valid RIR databaseARIN 668 99% 67
67.22.122.0/24 Valid RIR databaseARIN 668 99% 67
67.22.125.0/24 Valid RIR databaseARIN 668 99% 67
67.22.127.0/24 Valid RIR databaseARIN 668 99% 67
199.48.100.0/22 Valid RIR databaseARIN, RADB 668 99% 67
2602:ffc1::/36 Valid RIR databaseARIN 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS36731: ARIN::AS-SCCZIP. 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 (AS36731 isn't in the set, or no route object for AS36731 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 objectsAS36731 in itNot covered
ARIN::AS-SCCZIP ARIN 1116 Yes 1

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

  • ROA: none5
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none173.46.20.0/24No ROA covers it. Add a ROA for AS36731, maxLength 24.668 of 673
Route object: RIR173.46.20.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none173.46.22.0/24No ROA covers it. Add a ROA for AS36731, maxLength 24.668 of 673
Route object: RIR173.46.22.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none173.46.23.0/24No ROA covers it. Add a ROA for AS36731, maxLength 24.668 of 673
Route object: RIR173.46.23.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none173.46.24.0/23No ROA covers it. Add a ROA for AS36731, maxLength 23.668 of 673
Route object: RIR173.46.24.0/23Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none173.46.31.0/24No ROA covers it. Add a ROA for AS36731, maxLength 24.668 of 673
Route object: RIR173.46.31.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: none2602:ffc1::/32No route object for it. Add a route object with origin AS36731 in the RIR database for the space.632 of 636

Route objects not announced

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

67.22.121.0/24ARINInvalid: maxLength
67.22.123.0/24ARINInvalid: maxLength
67.22.124.0/24ARINInvalid: maxLength
67.22.126.0/24ARINInvalid: maxLength

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.