bgpreport

Network · data from 2026-11-12

AS30027 STINET-1

Registry name: STINET-1 - S & T COMMUNICATIONS LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30027, 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.
8.7.76.0/22 No ROA RIR databaseARIN 671 100% 68
2607:9600::/32 No ROA RIR databaseARIN 635 100% 69
68.232.48.0/20 Valid RIR databaseARIN 671 100% 68
192.160.54.0/24 Valid RIR databaseARIN 671 100% 68
207.195.128.0/19 Valid RIR databaseARIN 671 100% 68
208.84.76.0/22 Valid RIR databaseARIN 671 100% 68
216.144.96.0/20 Valid RIR databaseARIN 671 100% 68

AS-SET

AS30027's PeeringDB record names no 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 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none8.7.76.0/22No ROA covers it. Add a ROA for AS30027, maxLength 22.671 of 673
ROA: none2607:9600::/32No ROA covers it. Add a ROA for AS30027, maxLength 32.635 of 636

Route objects not announced

Every route object with origin AS30027 is announced.

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.