bgpreport

Network · data from 2026-11-12

AS13795 Smart Way Communications

Registry name: SMARTWAYCOMM - Smart Way Communications, LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13795, 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.68.152.0/21 No ROA None 2 0%low visibility 2
162.217.22.0/24 Valid Other origin onlycovered by 162.217.20.0/22 673 100% 67
23.152.144.0/24 Valid RIR databaseARIN 671 100% 68
23.152.145.0/24 Valid RIR databaseARIN 671 100% 68
74.123.209.0/24 Valid RIR databaseARIN 671 100% 68
74.123.210.0/24 Valid RIR databaseARIN 671 100% 68
74.123.211.0/24 Valid RIR databaseARIN 671 100% 68
74.123.212.0/24 Valid RIR databaseARIN 671 100% 68
74.123.213.0/24 Valid RIR databaseARIN 671 100% 68
74.123.214.0/24 Valid RIR databaseARIN 671 100% 68
142.249.143.0/24 Valid RIR databaseARIN 671 100% 68
207.90.216.0/22 Valid RIR databaseARIN 671 100% 68
208.78.200.0/21 Valid RIR databaseARIN 671 100% 68
74.123.215.0/24 Valid RIR databaseARIN 670 100% 68
208.78.200.0/24 Valid RIR databaseARIN 670 100% 68
208.78.201.0/24 Valid RIR databaseARIN 670 100% 68
208.78.204.0/24 Valid RIR databaseARIN 670 100% 68
208.78.205.0/24 Valid RIR databaseARIN 670 100% 68
208.78.206.0/24 Valid RIR databaseARIN 670 100% 68
208.78.207.0/24 Valid RIR databaseARIN 670 100% 68
162.217.20.0/24 Valid RIR databaseARIN 669 99% 67
162.217.21.0/24 Valid RIR databaseARIN 669 99% 67
162.217.23.0/24 Valid RIR databaseARIN 669 99% 67
2602:fd6c::/36 Valid RIR databaseARIN 634 100% 69
208.78.202.0/24 Valid RIR databaseARIN 98 15% 37
142.249.140.0/24 Valid RIR databaseARIN 73 11% 35
142.249.141.0/24 Valid RIR databaseARIN 73 11% 35
142.249.142.0/24 Valid RIR databaseARIN 73 11% 35
142.249.140.0/22 Valid RIR databaseARIN 67 10%low visibility 33
74.123.208.0/24 Valid RIR databaseARIN 66 10%low visibility 32
162.217.20.0/22 Valid RIR databaseARIN 64 10%low visibility 31
205.137.252.0/22 Valid RIR databaseARIN 64 10%low visibility 31

AS-SET

PeeringDB's irr_as_set for AS13795: AS-SWCOM. 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 (AS13795 isn't in the set, or no route object for AS13795 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 objectsAS13795 in itNot covered
AS-SWCOM ARIN 31128 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 18 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none38.68.152.0/21No ROA covers it. Add a ROA for AS13795, maxLength 21.2 of 673
Route object: none38.68.152.0/21No route object for it. Add a route object with origin AS13795 in the RIR database for the space.2 of 673
Route object: none162.217.22.0/24Route objects for it name AS25787, AS40496. A route object for 162.217.20.0/22 with origin AS13795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13795 in the RIR database for the space.673 of 673

Route objects not announced

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

74.123.208.0/21ARINValid
204.120.207.0/24RADBNo ROA
205.137.252.0/24ARINValid
205.137.253.0/24ARINValid
205.137.254.0/24ARINValid
205.137.255.0/24ARINValid
207.90.216.0/23ARINValid
207.90.216.0/24ARINValid
207.90.217.0/24ARINValid
207.90.218.0/23ARINValid
207.90.218.0/24ARINValid
207.90.219.0/24ARINValid
208.78.200.0/23ARINValid
208.78.203.0/24ARINValid
208.78.204.0/22ARINValid

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.