bgpreport

Network · data from 2026-11-12

AS46265 Netskrt (Canada)

Registry name: NETSKRTSYSTEMS-CANADA - Netskrt, CA · PeeringDB

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

Announced routes

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

38.88.78.0/23 Valid RIR databaseARIN 673 100% 67
208.52.176.0/24 Valid RIR databaseARIN 673 100% 67
2607:8240:2::/48 Valid RIR databaseARIN 634 100% 68
2607:8240:101::/48 Valid RIR databaseARIN 605 95% 67
2607:8240:dddd::/48 Valid RIR databaseARIN 1 0%low visibility 2
2607:8240:fffe::/48 Valid RIR databaseARIN 1 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS46265: AS-NETSKRT. 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 (AS46265 isn't in the set, or no route object for AS46265 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 objectsAS46265 in itNot covered
AS-NETSKRT ARIN 4168 Yes 0

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

  • Route object: not announced7

Route objects not announced

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

98.97.231.0/24ARINValid
207.22.36.0/24ARINValid
207.22.36.0/32ARINValid
208.52.177.0/24ARINValid
208.52.177.2/32ARINValid
2607:8240:ff0a::/48ARINValid
2607:8240:ff0b::/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.