bgpreport

Network · data from 2026-11-12

AS264124 SPEED SERVICE - INTERNET

Registry name: AS264124 - SPEED SERVICE - INTERNET, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264124, 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.
138.94.51.0/24 No ROA Other IRR onlyRADB, TC 672 100% 66
138.94.49.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
138.94.50.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
138.94.48.0/23 No ROA Other IRR onlyTC 669 99% 67
138.94.48.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
2804:22d0::/33 No ROA Other IRR onlyTC 636 100% 69
2804:22d0:8000::/33 No ROA Other IRR onlyTC 636 100% 69
2804:22d0::/34 No ROA Other IRR onlyTC 331 52% 65
2804:22d0:4000::/34 No ROA Other IRR onlyTC 331 52% 65
2804:22d0:8000::/34 No ROA Other IRR onlyTC 331 52% 65
2804:22d0:c000::/34 No ROA Other IRR onlyTC 331 52% 65
138.94.48.0/22 No ROA Other IRR onlyRADB, TC 130 19% 45

AS-SET

PeeringDB's irr_as_set for AS264124: AS264124. 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 (AS264124 isn't in the set, or no route object for AS264124 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 objectsAS264124 in itNot covered
AS264124 A single AS number, not a set: AS264124 (this network), 14 route objects.

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

  • ROA: none12
  • Route object: RIR12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none138.94.51.0/24No ROA covers it. Add a ROA for AS264124, maxLength 24.672 of 673
Route object: RIR138.94.51.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none138.94.49.0/24No ROA covers it. Add a ROA for AS264124, maxLength 24.671 of 673
Route object: RIR138.94.49.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none138.94.50.0/24No ROA covers it. Add a ROA for AS264124, maxLength 24.671 of 673
Route object: RIR138.94.50.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none138.94.48.0/23No ROA covers it. Add a ROA for AS264124, maxLength 23.669 of 673
Route object: RIR138.94.48.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none138.94.48.0/24No ROA covers it. Add a ROA for AS264124, maxLength 24.668 of 673
Route object: RIR138.94.48.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:22d0::/33No ROA covers it. Add a ROA for AS264124, maxLength 33.636 of 636
Route object: RIR2804:22d0::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:22d0:8000::/33No ROA covers it. Add a ROA for AS264124, maxLength 33.636 of 636
Route object: RIR2804:22d0:8000::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:22d0::/34No ROA covers it. Add a ROA for AS264124, maxLength 34.331 of 636
Route object: RIR2804:22d0::/34Route object only in TC. Add it in the RIR database for the space.331 of 636
ROA: none2804:22d0:4000::/34No ROA covers it. Add a ROA for AS264124, maxLength 34.331 of 636
Route object: RIR2804:22d0:4000::/34Route object only in TC. Add it in the RIR database for the space.331 of 636
ROA: none2804:22d0:8000::/34No ROA covers it. Add a ROA for AS264124, maxLength 34.331 of 636
Route object: RIR2804:22d0:8000::/34Route object only in TC. Add it in the RIR database for the space.331 of 636
ROA: none2804:22d0:c000::/34No ROA covers it. Add a ROA for AS264124, maxLength 34.331 of 636
Route object: RIR2804:22d0:c000::/34Route object only in TC. Add it in the RIR database for the space.331 of 636
ROA: none138.94.48.0/22No ROA covers it. Add a ROA for AS264124, maxLength 22.130 of 673
Route object: RIR138.94.48.0/22Route object only in RADB, TC. Add it in the RIR database for the space.130 of 673

Route objects not announced

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

138.94.50.0/23TCNo ROA
2804:22d0::/32RADB, TCNo ROA

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.