bgpreport

Network · data from 2026-11-12

AS4593

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

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

95.135.203.0/24 Invalid: origin Other origin only 1 0%low visibility 1
138.226.219.0/24 Valid Nonecovered by 138.226.218.0/23 672 100% 67
138.226.218.0/24 Valid Nonecovered by 138.226.218.0/23 669 99% 67
48.45.192.0/24 Valid RIR databaseARIN 672 100% 67
48.45.193.0/24 Valid RIR databaseARIN 672 100% 67
48.45.194.0/24 Valid RIR databaseARIN 672 100% 67
48.45.195.0/24 Valid RIR databaseARIN 672 100% 67
48.45.196.0/24 Valid RIR databaseARIN 672 100% 67
48.45.198.0/24 Valid RIR databaseARIN 672 100% 67
48.45.199.0/24 Valid RIR databaseARIN 672 100% 67
48.45.200.0/24 Valid RIR databaseARIN 672 100% 67
48.45.220.0/24 Valid RIR databaseARIN 672 100% 66
48.45.221.0/24 Valid RIR databaseARIN 672 100% 66
48.45.222.0/24 Valid RIR databaseARIN 672 100% 66
48.45.223.0/24 Valid RIR databaseARIN 672 100% 66
79.98.180.0/24 Valid RIR databaseRIPE 672 100% 67
87.85.225.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
141.11.44.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
2.26.216.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
2.26.219.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
48.45.224.0/24 Valid RIR databaseARIN 671 100% 66
48.45.225.0/24 Valid RIR databaseARIN 671 100% 66
163.8.221.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
178.83.153.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
178.214.208.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
188.209.137.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
188.209.139.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
2.26.176.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
48.45.197.0/24 Valid RIR databaseARIN 669 99% 67

AS-SET

AS4593 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: origin1
  • Route object: none3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin95.135.203.0/24ROAs covering it name AS20473, AS55177, AS152726, not AS4593. If AS4593 should announce it, add a ROA for AS4593.1 of 673
Route object: none95.135.203.0/24Route objects for it name AS55177, AS152726. Add a route object with origin AS4593 in the RIR database for the space.1 of 673
Route object: none138.226.219.0/24No route object for it. A route object for 138.226.218.0/23 with origin AS4593 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4593 in the RIR database for the space.672 of 673
Route object: none138.226.218.0/24No route object for it. A route object for 138.226.218.0/23 with origin AS4593 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4593 in the RIR database for the space.669 of 673

Route objects not announced

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

48.45.192.0/21ARINValid
48.45.200.0/22ARINValid
48.45.201.0/24ARINValid
48.45.202.0/24ARINValid
48.45.203.0/24ARINValid
48.45.220.0/22ARINValid
48.45.224.0/23ARINValid
138.226.218.0/23RIPEValid

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.