bgpreport

Network · data from 2026-11-12

AS274749 Speed Connect

Registry name: AS274749 - Speed Connect, BR · PeeringDB

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

Announced routes

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

2804:9304::/35 Valid Nonecovered by 2804:9304::/34 631 99% 67
2804:9304:2000::/35 Valid Nonecovered by 2804:9304::/34 631 99% 67
2804:9304:4000::/35 Valid Nonecovered by 2804:9304:4000::/34 631 99% 67
2804:9304:6000::/35 Valid Nonecovered by 2804:9304:4000::/34 631 99% 67
2804:9304:8000::/35 Valid Nonecovered by 2804:9304:8000::/34 631 99% 67
2804:9304:a000::/35 Valid Nonecovered by 2804:9304:8000::/34 631 99% 67
2804:9304::/33 Valid Other IRR onlyRADB, TC 631 99% 67
2804:9304::/34 Valid Other IRR onlyRADB, TC 631 99% 67
2804:9304:4000::/34 Valid Other IRR onlyRADB, TC 631 99% 67
2804:9304:8000::/34 Valid Other IRR onlyRADB, TC 631 99% 67

AS-SET

PeeringDB's irr_as_set for AS274749: AS274749:AS-SPEEDCONNECT-ALL. 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 (AS274749 isn't in the set, or no route object for AS274749 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 objectsAS274749 in itNot covered
AS274749:AS-SPEEDCONNECT-ALL TC 5356 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 24 are in fix.csv.

  • Route object: none6
  • Route object: RIR4
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: none2804:9304::/35No route object for it. A route object for 2804:9304::/34 with origin AS274749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274749 in the RIR database for the space.631 of 636
Route object: none2804:9304:2000::/35No route object for it. A route object for 2804:9304::/34 with origin AS274749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274749 in the RIR database for the space.631 of 636
Route object: none2804:9304:4000::/35No route object for it. A route object for 2804:9304:4000::/34 with origin AS274749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274749 in the RIR database for the space.631 of 636
Route object: none2804:9304:6000::/35No route object for it. A route object for 2804:9304:4000::/34 with origin AS274749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274749 in the RIR database for the space.631 of 636
Route object: none2804:9304:8000::/35No route object for it. A route object for 2804:9304:8000::/34 with origin AS274749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274749 in the RIR database for the space.631 of 636
Route object: none2804:9304:a000::/35No route object for it. A route object for 2804:9304:8000::/34 with origin AS274749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274749 in the RIR database for the space.631 of 636
Route object: RIR2804:9304::/33Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:9304::/34Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:9304:4000::/34Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:9304:8000::/34Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

2804:9304::/32ALTDB, RADB, TCValid
2804:9304::/40RADBValid
2804:9304:100::/40RADBValid
2804:9304:200::/40RADBValid
2804:9304:300::/40RADBValid
2804:9304:400::/40RADBValid
2804:9304:500::/40RADBValid
2804:9304:600::/40RADBValid
2804:9304:700::/40RADBValid
2804:9304:800::/40RADBValid
2804:9304:900::/40RADBValid
2804:9304:1300::/40RADBValid
2804:9304:8000::/33RADB, TCValid
2804:9304:c000::/34TCValid

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.