bgpreport

Network · data from 2026-11-12

AS264939 REALNET MG

Registry name: AS264939 - REALNET MG, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264939, 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:3040::/32 No ROA None 635 100% 67
2804:3040::/33 No ROA None 349 55% 64
2804:3040::/34 No ROA None 349 55% 64
2804:3040:4000::/34 No ROA None 349 55% 64
2804:3040:8000::/33 No ROA None 349 55% 64
2804:3040:8000::/34 No ROA None 349 55% 64
2804:3040:c000::/34 No ROA None 349 55% 64
168.228.152.0/23 No ROA Nonecovered by 168.228.152.0/22 198 29% 54
168.228.154.0/23 No ROA Nonecovered by 168.228.152.0/22 198 29% 54
168.228.152.0/22 No ROA Other IRR onlyRADB 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS264939: AS264939: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 (AS264939 isn't in the set, or no route object for AS264939 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 objectsAS264939 in itNot covered
AS264939:AS-CONE In no IRR database read today.

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

  • ROA: none10
  • Route object: none9
  • Route object: RIR1
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none2804:3040::/32No ROA covers it. Add a ROA for AS264939, maxLength 32.635 of 636
Route object: none2804:3040::/32No route object for it. Add a route object with origin AS264939 in the RIR database for the space.635 of 636
ROA: none2804:3040::/33No ROA covers it. Add a ROA for AS264939, maxLength 33.349 of 636
Route object: none2804:3040::/33No route object for it. Add a route object with origin AS264939 in the RIR database for the space.349 of 636
ROA: none2804:3040::/34No ROA covers it. Add a ROA for AS264939, maxLength 34.349 of 636
Route object: none2804:3040::/34No route object for it. Add a route object with origin AS264939 in the RIR database for the space.349 of 636
ROA: none2804:3040:4000::/34No ROA covers it. Add a ROA for AS264939, maxLength 34.349 of 636
Route object: none2804:3040:4000::/34No route object for it. Add a route object with origin AS264939 in the RIR database for the space.349 of 636
ROA: none2804:3040:8000::/33No ROA covers it. Add a ROA for AS264939, maxLength 33.349 of 636
Route object: none2804:3040:8000::/33No route object for it. Add a route object with origin AS264939 in the RIR database for the space.349 of 636
ROA: none2804:3040:8000::/34No ROA covers it. Add a ROA for AS264939, maxLength 34.349 of 636
Route object: none2804:3040:8000::/34No route object for it. Add a route object with origin AS264939 in the RIR database for the space.349 of 636
ROA: none2804:3040:c000::/34No ROA covers it. Add a ROA for AS264939, maxLength 34.349 of 636
Route object: none2804:3040:c000::/34No route object for it. Add a route object with origin AS264939 in the RIR database for the space.349 of 636
ROA: none168.228.152.0/23No ROA covers it. Add a ROA for AS264939, maxLength 23.198 of 673
Route object: none168.228.152.0/23No route object for it. A route object for 168.228.152.0/22 with origin AS264939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264939 in the RIR database for the space.198 of 673
ROA: none168.228.154.0/23No ROA covers it. Add a ROA for AS264939, maxLength 23.198 of 673
Route object: none168.228.154.0/23No route object for it. A route object for 168.228.152.0/22 with origin AS264939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264939 in the RIR database for the space.198 of 673
ROA: none168.228.152.0/22No ROA covers it. Add a ROA for AS264939, maxLength 22.672 of 673
Route object: RIR168.228.152.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
AS-SET: not foundAS264939:AS-CONEPeeringDB names AS264939:AS-CONE; no IRR database read has it.

Route objects not announced

Every route object with origin AS264939 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.