bgpreport

Network · data from 2026-11-12

AS17267 VGI Technology, Inc.

Registry name: VGI-TECHNOLOGY - VGI Technology, Inc., US · PeeringDB

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

Announced routes

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

23.149.240.0/24 No ROA RIR databaseARIN 669 99% 68
38.65.80.0/24 Valid RIR databaseARIN 670 100% 68
165.140.66.0/24 Valid RIR databaseARIN 670 100% 68
23.177.248.0/24 Valid RIR databaseARIN 669 99% 68
165.140.64.0/24 Valid RIR databaseARIN 669 99% 68
165.140.65.0/24 Valid RIR databaseARIN 669 99% 68
165.140.67.0/24 Valid RIR databaseARIN 669 99% 68
199.89.49.0/24 Valid RIR databaseARIN 668 99% 67
2602:f2f6::/40 Valid RIR databaseARIN 635 100% 69
2602:fd97::/32 Valid RIR databaseARIN 635 100% 69
184.105.110.0/24 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS17267: AS17267:AS-VGITECHNOLOGY. 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 (AS17267 isn't in the set, or no route object for AS17267 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 objectsAS17267 in itNot covered
AS17267:AS-VGITECHNOLOGY 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 8 are in fix.csv.

  • ROA: none1
  • AS-SET: not found1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none23.149.240.0/24No ROA covers it. Add a ROA for AS17267, maxLength 24.669 of 673
AS-SET: not foundAS17267:AS-VGITECHNOLOGYPeeringDB names AS17267:AS-VGITECHNOLOGY; no IRR database read has it.

Route objects not announced

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

38.121.36.0/24ARINValid
38.134.10.0/24ARINValid
2001:470:2ff::/48ARINValid
2602:fd97::/48ARINValid
2602:fd97:1::/48ARINValid
2602:fd97:1000::/36ARINValid

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.