bgpreport

Network · data from 2026-11-12

AS10946 Network Time Foundation, Inc.

Registry name: ASN-NTF - Network Time Foundation, Inc., US · PeeringDB

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

Announced routes

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

104.152.84.0/24 No ROA Nonecovered by 104.152.84.0/22 669 99% 68
104.152.84.0/22 No ROA RIR databaseARIN 669 99% 68

AS-SET

PeeringDB's irr_as_set for AS10946: ARIN::AS-10946-NTF. 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 (AS10946 isn't in the set, or no route object for AS10946 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 objectsAS10946 in itNot covered
ARIN::AS-10946-NTF ARIN 113 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 5 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none104.152.84.0/24No ROA covers it. Add a ROA for AS10946, maxLength 24.669 of 673
Route object: none104.152.84.0/24No route object for it. A route object for 104.152.84.0/22 with origin AS10946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10946 in the RIR database for the space.669 of 673
ROA: none104.152.84.0/22No ROA covers it. Add a ROA for AS10946, maxLength 22.669 of 673

Route objects not announced

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

174.46.75.0/24RADBNo ROA
2602:804:2000::/44ARINNo 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.