bgpreport

Network · data from 2026-11-12

AS34553 Nathan Sales

Registry name: NATHANSALES - Packetframe, US · PeeringDB

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

Announced routes

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

2602:809:3001::/48 No ROA RIR databaseARIN 633 100% 69
45.59.141.0/24 Valid RIR databaseARIN 671 100% 68
45.59.140.0/24 Valid RIR databaseARIN 670 100% 68
2602:809:3008::/48 Valid RIR databaseARIN 635 100% 70
23.141.112.0/24 Valid RIR databaseARIN 4 1%low visibility 3
2602:809:3009::/48 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS34553: AS34553:AS-ALL. 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 (AS34553 isn't in the set, or no route object for AS34553 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 objectsAS34553 in itNot covered
AS34553:AS-ALL RIPE1 member set in no database: AS44977:AS-ALL 102103 Yes 0
ARIN (also)1 member set in no database: AS44977:AS-ALL 114107 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 8 are in fix.csv.

  • ROA: none1
  • AS-SET: missing member1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2602:809:3001::/48No ROA covers it. Add a ROA for AS34553, maxLength 48.633 of 636
AS-SET: missing memberAS34553:AS-ALLAS34553:AS-ALL (RIPE) lists AS44977:AS-ALL; no IRR database read has it.

Route objects not announced

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

44.26.163.0/24ALTDBNo ROA
66.248.234.0/24ARINInvalid: origin
66.248.235.0/24ARINInvalid: origin
2602:809:3000::/48ARINNo ROA
2602:809:3004::/48ARINValid
2602:809:300a::/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.