Bandwidth Limit Sample Clauses

A Bandwidth Limit clause sets a maximum threshold on the amount of data that can be transmitted or received over a network connection within a specified period. In practice, this clause may apply to internet service agreements, cloud hosting contracts, or data transfer arrangements, where exceeding the set bandwidth cap could result in additional charges, throttled speeds, or service suspension. Its core function is to manage network resources efficiently and prevent excessive usage that could impact service quality or operational costs.
Bandwidth Limit. Network services at the University are a shared and limited resource. In order to conserve that resource, access to the Internet from the University’s residences is also governed by the following University Regulations: (i) The University does not provide unlimited access to the Internet. (ii) The University provides Internet access for the purpose of furthering the academic careers of students. Some personal use of such access may be permitted, provided it is legal and restrained to not consume excessive bandwidth. Examples of uses that consume excessive bandwidth are Peer to Peer file sharing programs, frequent transfers of large files and receiving or sending continuous live audio, video and movies. These activities may be blocked at any time at the discretion of the University’s Computing and Network Services. (iii) The limit applies to all inbound and outbound traffic. (iv) The permissible bandwidth limit will be determined by the University’s Computing and Network Services; no traffic data will be posted in publicly accessible forms. (v) The limit applies to traffic to/from the Residence from/to the Internet. Traffic to/from campus facilities is subject to this limit. (vi) Students may not acquire Internet access from commercial providers. (vii) Students may be subject to other University sanctions policy based on their permissible traffic levels, Host / Port Scanning, Virus / Worm Backdoors, SMTP Relay / Spamming, Botnet membership, which can be found at: ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇▇.▇▇/net-ops/security/traffic.htm (viii) Students who attempt to circumvent these Regulations through technical means (such as changing ports or subverting other campus facilities) will face permanent denial of network access, and possible sanctions under the Chestnut Residence Code of Conduct and/or U of T Student Code of Conduct. P: 416-585-3160 | E: ▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇.▇▇ ▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇
View SourceView Similar (4)
Bandwidth Limit. Network services at the University are a shared and limited resource. In order to conserve that resource, access to the Internet from the University’s residences is also governed by the following University Regulations: i. The University does not provide unlimited access to the Internet. ii. The University provides Internet access for the purpose of furthering the academic careers of students. Some personal use of such access may be permitted, provided it is legal and restrained to not consume excessive bandwidth. Examples of uses that consume excessive bandwidth are Peer to Peer file sharing programs, frequent transfers of large files and receiving or sending continuous live audio, video and movies. These activities may be blocked at any time at the discretion of the University’s Computing and Network Services. iii. The limit applies to all inbound and outbound traffic. iv. The permissible bandwidth limit will be determined by the University’s Computing and Network Services; no traffic data will be posted in publicly accessible forms. v. The limit applies to traffic to/from the Residence from/to the Internet. Traffic to/from campus facilities is subject to this limit. vi. Students may not acquire Internet access from commercial providers. vii. Students may be subject to other University sanctions policy based on their permissible traffic levels, Host / Port Scanning, Virus / Worm Backdoors, SMTP Relay / Spamming, Botnet membership. viii. Students who attempt to circumvent these Regulations through technical means (such as changing ports or subverting other campus facilities) will face permanent denial of network access, and possible sanctions under the Chestnut Residence Code of Conduct and/or U of T Student Code of Conduct.
View SourceView Similar (4)

Related to Bandwidth Limit

  • Bandwidth the amount of data (quantified as “Mbps” or “Gbps”) made available to Customer as specified in a Service Order.

  • Personal Car Usage 7.1 Personal vehicle usage will be reimbursed in an amount equal to the standard mileage rate allowed by the IRS. 7.2 Per code of Federal Regulations, Title 26, Subtitle A, Chapter 1, Subchapter B, Part IX, Section 274(d), all expense reimbursement requests must include the following: 7.2.1.1 Date 7.2.1.2 Destination 7.2.1.3 Purpose 7.2.1.4 Name of traveler(s) 7.2.1.5 Correspondence that verifies business purpose of the expense 7.3 The mileage for a personal vehicle must document the date, location of travel to/from, number of miles traveled and purpose of trip. 7.4 Mileage will be reimbursed on the basis of the most commonly used route. 7.5 Reimbursement for mileage shall not exceed the cost of a round trip coach airfare. 7.6 Reimbursement for mileage shall be prohibited between place of residence and usual place of work. 7.7 Mileage should be calculated from employee’s regular place of work or their residence, whichever is the shorter distance when traveling to a meeting or traveling to Williamson County, Texas for vendors who are located outside of the Williamson County Courthouse, ▇▇▇ ▇▇▇▇ ▇▇▇▇▇▇, ▇▇▇▇▇▇▇▇▇▇, ▇▇▇▇▇ ▇▇▇▇▇ by at least a 45-mile radius. 7.8 When more than one person travels in same vehicle, only one person may claim mileage reimbursement. 7.9 Tolls, if reasonable, are reimbursable. Receipts are required for reimbursement. If a receipt is not obtainable, then written documentation of expense must be submitted for reimbursement (administrative fees on Tolls will not be reimbursed). 7.10 Parking fees, if reasonable are reimbursable for meetings and hotel stays. For vendors who contract with a third party for visitor parking at vendor’s place of business, Williamson County will not reimburse a vendor based on a percentage of its contracted visitor parking fees. Rather, Williamson County will reimburse Vendor for visitor parking on an individual basis for each time a visitor uses Vendor’s visitor parking. Receipts are required for reimbursement. If a receipt is not obtainable, then written documentation of expense must be submitted for reimbursement. 7.11 Operating and maintenance expenses as well as other personal expenses, such as parking tickets, traffic violations, and car repairs and collision damage are not reimbursable.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • System Availability Although we will try to provide continuous access to the Service, we cannot and do not guarantee that the Service will be available 100% of the time and will not be liable in the event Service is unavailable. Actual service or network performance is dependent on a variety of factors outside of our control. If you notify us within twenty-four (24) hours and we confirm an outage consisting of a period of two (2) hours in any calendar month, and not due to any service, act, or omission of you, a third party, your applications, equipment or facilities, or reasons outside of our control, you shall be eligible for a service credit. A service credit shall be computed as a pro-rated charge for one day of the regular monthly fees for the Service in the next monthly statement. Intermittent service outages for periods of less than two (2) hours are not considered service outages. Outages caused by routine scheduled maintenance are also not considered an outage. You shall receive advance notice no less than forty-eight (48) hours in advance of our scheduled maintenance. Scheduled maintenance will be performed between 12:00 a.m. and 6:00 a.m. CST.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.