bgpreport

Network · data from 2026-11-12

AS36014 ONE-STOP-INTERNET

Registry name: ONE-STOP-INTERNET - One-Stop Communications of PA Inc, US · PeeringDB

8IPv4 routes 87.5% RPKI valid · 75.0% 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
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS36014, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS36014, 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.
206.80.235.0/24 No ROA Other IRR onlyRADB 669 99% 67
199.202.224.0/24 Valid Nonecovered by 199.202.224.0/22 671 100% 67
199.202.227.0/24 Valid Nonecovered by 199.202.224.0/22 671 100% 67
136.175.64.0/23 Valid RIR databaseARIN, RADB 671 100% 67
162.251.112.0/22 Valid RIR databaseARIN, RADB 671 100% 67
167.253.80.0/22 Valid RIR databaseARIN, RADB 671 100% 67
207.168.112.0/23 Valid RIR databaseARIN, RADB 671 100% 67
216.132.144.0/22 Valid RIR databaseARIN 671 100% 67
2607:c40::/32 Valid RIR databaseARIN, RADB 635 100% 68

AS-SET

PeeringDB's irr_as_set for AS36014: RADB::AS36014:AS-CONE. 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 (AS36014 isn't in the set, or no route object for AS36014 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 objectsAS36014 in itNot covered
RADB::AS36014:AS-CONE RADB 119 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 6 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none206.80.235.0/24No ROA covers it. Add a ROA for AS36014, maxLength 24.669 of 673
Route object: RIR206.80.235.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: none199.202.224.0/24No route object for it. A route object for 199.202.224.0/22 with origin AS36014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36014 in the RIR database for the space.671 of 673
Route object: none199.202.227.0/24No route object for it. A route object for 199.202.224.0/22 with origin AS36014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36014 in the RIR database for the space.671 of 673

Route objects not announced

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

64.234.228.0/22ARIN, RADBValid
199.202.224.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.