bgpreport

Network · data from 2026-11-12

AS272730 Pedra Net

Registry name: AS272730 - Wellington Paiva Damascena - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272730, 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:87c4:4000::/38 Valid Nonecovered by 2804:87c4:4000::/34 634 100% 67
2804:87c4:4000::/40 Valid Nonecovered by 2804:87c4:4000::/34 634 100% 67
2804:87c4:4100::/40 Valid Nonecovered by 2804:87c4:4000::/34 634 100% 67
2804:87c4:4200::/40 Valid Nonecovered by 2804:87c4:4000::/34 634 100% 67
2804:87c4:4300::/40 Valid Nonecovered by 2804:87c4:4000::/34 634 100% 67
2804:87c4:4400::/38 Valid Nonecovered by 2804:87c4:4000::/34 634 100% 67
2804:87c4:4400::/40 Valid Nonecovered by 2804:87c4:4000::/34 634 100% 67
2804:87c4:4500::/40 Valid Nonecovered by 2804:87c4:4000::/34 634 100% 67
2804:87c4:4800::/38 Valid Nonecovered by 2804:87c4:4000::/34 634 100% 67
2804:87c4:4040::/46 Valid Nonecovered by 2804:87c4:4000::/34 633 100% 67
2804:87c4:5000::/40 Valid Nonecovered by 2804:87c4:4000::/34 633 100% 67
170.80.60.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
2804:87c4::/32 Valid Other IRR onlyRADB, TC 635 100% 69
2804:87c4:4000::/34 Valid Other IRR onlyRADB, TC 633 100% 67
2804:87c4::/33 Valid Other IRR onlyRADB, TC 349 55% 64
2804:87c4:8000::/33 Valid Other IRR onlyTC 349 55% 64
170.80.60.0/23 Valid Other IRR onlyTC 199 30% 55
170.80.62.0/23 Valid Other IRR onlyTC 199 30% 55

AS-SET

PeeringDB's irr_as_set for AS272730: AS272730:AS-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 (AS272730 isn't in the set, or no route object for AS272730 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 objectsAS272730 in itNot covered
AS272730:AS-ALL TC 2230 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 27 are in fix.csv.

  • Route object: none11
  • Route object: RIR7
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none2804:87c4:4000::/38No route object for it. A route object for 2804:87c4:4000::/34 with origin AS272730 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272730 in the RIR database for the space.634 of 636
Route object: none2804:87c4:4000::/40No route object for it. A route object for 2804:87c4:4000::/34 with origin AS272730 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272730 in the RIR database for the space.634 of 636
Route object: none2804:87c4:4100::/40No route object for it. A route object for 2804:87c4:4000::/34 with origin AS272730 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272730 in the RIR database for the space.634 of 636
Route object: none2804:87c4:4200::/40No route object for it. A route object for 2804:87c4:4000::/34 with origin AS272730 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272730 in the RIR database for the space.634 of 636
Route object: none2804:87c4:4300::/40No route object for it. A route object for 2804:87c4:4000::/34 with origin AS272730 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272730 in the RIR database for the space.634 of 636
Route object: none2804:87c4:4400::/38No route object for it. A route object for 2804:87c4:4000::/34 with origin AS272730 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272730 in the RIR database for the space.634 of 636
Route object: none2804:87c4:4400::/40No route object for it. A route object for 2804:87c4:4000::/34 with origin AS272730 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272730 in the RIR database for the space.634 of 636
Route object: none2804:87c4:4500::/40No route object for it. A route object for 2804:87c4:4000::/34 with origin AS272730 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272730 in the RIR database for the space.634 of 636
Route object: none2804:87c4:4800::/38No route object for it. A route object for 2804:87c4:4000::/34 with origin AS272730 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272730 in the RIR database for the space.634 of 636
Route object: none2804:87c4:4040::/46No route object for it. A route object for 2804:87c4:4000::/34 with origin AS272730 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272730 in the RIR database for the space.633 of 636
Route object: none2804:87c4:5000::/40No route object for it. A route object for 2804:87c4:4000::/34 with origin AS272730 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272730 in the RIR database for the space.633 of 636
Route object: RIR170.80.60.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:87c4::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:87c4:4000::/34Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:87c4::/33Route object only in RADB, TC. Add it in the RIR database for the space.349 of 636
Route object: RIR2804:87c4:8000::/33Route object only in TC. Add it in the RIR database for the space.349 of 636
Route object: RIR170.80.60.0/23Route object only in TC. Add it in the RIR database for the space.199 of 673
Route object: RIR170.80.62.0/23Route object only in TC. Add it in the RIR database for the space.199 of 673

Route objects not announced

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

170.80.60.0/24RADB, TCValid
170.80.61.0/24RADB, TCValid
170.80.62.0/24RADB, TCValid
170.80.63.0/24RADB, TCValid
179.63.67.0/24RADBNo ROA
2804:7d40:c000::/34RADBNo ROA
2804:87c4::/34RADB, TCValid
2804:87c4:8000::/34RADB, TCValid
2804:87c4: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.